Skip to content

v1.2.0

Choose a tag to compare

View all tags
@k-t18 k-t18 released this 04 Oct 11:27
· 4 commits to main since this release
v1.2.0
e9fc4a4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.2.0 — From spec to pull request

This release adds a complete workflow around the existing build skills. Until now the kit helped developers build (tokens, feature slices, components, design QA, native port). It now also covers what comes before and after: writing down how a flow should behave, turning that into GitHub issues, and checking the work before it is merged.

The workflow

/spec-builder → /spec-challenger → PM approves → /spec-issues → build → /ship

/ship runs lint and type-check, /design-qa, /pr-check, /security-check, /flow-test and /docs-sync in order, stops on a blocker, and opens the pull request. Merging stays a human decision.

New commands

Command Who runs it What it does
/agentic-dev-kit:spec-builder PM Interviews the PM and writes a flow's functional spec to docs/specs/<flow-name>/spec.md.
/agentic-dev-kit:spec-challenger Developer Challenges the spec before approval and raises the doubts a developer would hit mid-build.
/agentic-dev-kit:spec-issues PM or lead Turns an approved spec's work breakdown into a GitHub epic and child issues.
/agentic-dev-kit:pr-check Developer Reviews a branch against the spec and the rules in CLAUDE.md.
/agentic-dev-kit:security-check Developer Reviews the frontend changes for security problems.
/agentic-dev-kit:flow-test Developer Checks acceptance criteria on the running web app, in the browser.
/agentic-dev-kit:docs-sync Developer Brings the spec, feature doc, changelog and README in line with what was built.
/agentic-dev-kit:ship Developer Runs the checks in order and opens the PR with one combined report.

What each one does

Functional specs

  • /spec-builder asks questions in rounds (why, scope, the flow screen by screen, branches, APIs, offline, errors, sensitive data) and never invents an answer. Anything unanswered becomes an open question with an owner.
  • The spec has 16 sections. Screens, steps, rules, APIs, acceptance criteria, open questions and work items each get a permanent ID (S-, F-, R-, API-, AC-, Q-, W-), so later work can point at them.
  • When a Figma link is given, the screen list is read from the Figma file.
  • A spec stays Draft while a blocking question is open. Only the PM's confirmation makes it Approved.
  • /spec-challenger is a read-only agent that checks the spec against itself, the Figma file and the codebase. Doubts the developer agrees with are added to the spec's open questions, tagged [challenge].

Issues

  • /spec-issues works on Approved specs only. It creates one epic and one child issue per work item, in dependency order, and writes the issue numbers back into the spec.
  • Issues follow the project's feature-request issue template in .github/ISSUE_TEMPLATE/. Titles are feat(<flow-name>:W-01): <piece of work> and feat(<flow-name>:epic): <flow name>.
  • It shows the full plan and asks once before creating anything, and it does not create duplicates when run again.

Checks

  • /pr-check and /security-check use read-only agents. They report first, then fix only what the developer agrees to. Reports are posted to the PR only when asked.
  • /flow-test drives the developer's own Chrome through the Claude in Chrome extension. It reports pass, fail or could-not-test per acceptance criterion, with console and network evidence, and saves rerunnable test files in the project's existing end-to-end runner.
  • /docs-sync shows every planned document edit and writes only what the developer agrees to. Where the code differs from the spec, it raises a [drift] question for the PM instead of rewriting the spec.

Works without a spec too

For a bug fix or small change raised straight as an issue, /pr-check, /security-check, /docs-sync and /ship run on the branch's changes and skip only their spec-based checks. /flow-test #<issue> tests against the issue's stated expected behaviour. Only /spec-issues needs a spec.

Fixes

  • Skills now use the @app/* and @8848digital/* workspace package scopes consistently.
  • feature-slice imports chassis symbols from @8848digital/catalyst.

Upgrading

  1. Update the plugin in Claude Code: /plugin marketplace update agentic-dev-kit, then restart.
  2. In each project, run /agentic-dev-kit:init-dev-kit and choose merge, to bring the new guardrails into the project's CLAUDE.md.

What you need

  • GitHub CLI (gh), signed in, for /spec-issues, /ship and posting reports to a PR.
  • Figma MCP connected, for reading screens in /spec-builder and /spec-challenger.
  • Claude in Chrome extension, for /flow-test.

Known limitations

  • /flow-test covers the web app only. Native testing stays manual.
  • The checks do not replace human review. Sync and offline behaviour, SQL correctness and behaviour on real devices still need a person.

Full Changelog: v1.1.0...v1.2.0

Assets 2
Loading