Skip to content

DataArt/artisyn-implementation-harness / skills/implementation-harness

implementation-harness

Flagged

Install the portable AI-dev harness, rebuild its operational graph standalone, harvest project skill improvements into its canonical templates, package direct canonical edits into a portable bundle, or apply canonical updates to an existing project. Use /implementation-harness launch, /implementation-harness reindex-graph, or /implementation-harness patch harvest|prepare|apply.

FileKindSize
CHANGELOG.mdmarkdown37.5 KB
README.mdmarkdown13.7 KB
SKILL.mdskill md9.6 KB
bin/artisyn-implementation-harness.mjsexecutablescript11.8 KB
bin/lib/placer.mjsscript2.6 KB
bin/lib/providers.mjsscript1.8 KB
bin/lib/reporter.mjsscript3.0 KB
bin/lib/zip.mjsscript4.0 KB
canonical/adaptors/claude/browser.mdmarkdown2.5 KB
canonical/adaptors/claude/context.mdmarkdown517 B
canonical/adaptors/claude/credentials.mdmarkdown512 B
canonical/adaptors/claude/delegation.mdmarkdown910 B
canonical/adaptors/claude/interaction.mdmarkdown359 B
canonical/adaptors/claude/planning.mdmarkdown745 B
canonical/adaptors/claude/review.mdmarkdown1.0 KB
canonical/adaptors/claude/task-tracking.mdmarkdown897 B
canonical/adaptors/codex/browser.mdmarkdown1.0 KB
canonical/adaptors/codex/context.mdmarkdown517 B
canonical/adaptors/codex/credentials.mdmarkdown480 B
canonical/adaptors/codex/delegation.mdmarkdown910 B
canonical/adaptors/codex/interaction.mdmarkdown359 B
canonical/adaptors/codex/planning.mdmarkdown904 B
canonical/adaptors/codex/review.mdmarkdown973 B
canonical/adaptors/codex/task-tracking.mdmarkdown1.1 KB
canonical/adaptors/copilot/browser.mdmarkdown620 B
canonical/adaptors/copilot/context.mdmarkdown881 B
canonical/adaptors/copilot/credentials.mdmarkdown992 B
canonical/adaptors/copilot/delegation.mdmarkdown1.2 KB
canonical/adaptors/copilot/interaction.mdmarkdown454 B
canonical/adaptors/copilot/planning.mdmarkdown785 B
canonical/adaptors/copilot/review.mdmarkdown791 B
canonical/adaptors/copilot/task-tracking.mdmarkdown723 B
canonical/agents/architect/INTENT.mdmarkdown2.4 KB
canonical/agents/architect/TEMPLATE.mdmarkdown6.5 KB
canonical/agents/docs-writer/INTENT.mdmarkdown2.2 KB
canonical/agents/docs-writer/TEMPLATE.mdmarkdown2.8 KB
canonical/agents/infra/INTENT.mdmarkdown2.1 KB
canonical/agents/infra/TEMPLATE.mdmarkdown5.1 KB
canonical/agents/layer/INTENT.mdmarkdown6.0 KB
canonical/agents/layer/TEMPLATE.mdmarkdown1.5 KB
canonical/agents/onboarding/INTENT.mdmarkdown5.3 KB
canonical/agents/onboarding/TEMPLATE.mdmarkdown4.2 KB
canonical/agents/product-architect/INTENT.mdmarkdown7.5 KB
canonical/agents/product-architect/TEMPLATE.mdmarkdown3.9 KB
canonical/agents/scrum-master/INTENT.mdmarkdown10.9 KB
canonical/agents/scrum-master/TEMPLATE.mdmarkdown12.3 KB
canonical/docs/.og/cli.mjsscript13.6 KB
canonical/docs/.og/cli.test.mjsscript19.6 KB
canonical/docs/.og/constants.mjsscript2.9 KB
canonical/docs/.og/docs-operational-graph.sqlitebinary24.0 KB
canonical/docs/.og/docs.mjsscript5.5 KB
canonical/docs/.og/edges.mjsscript5.8 KB
canonical/docs/.og/schema.mjsscript741 B
canonical/docs/.og/utils.mjsscript5.2 KB
canonical/docs/Engineering Guide/01 Conventions.mdmarkdown3.0 KB
canonical/docs/Engineering Guide/03 Engineer Role.mdmarkdown2.6 KB
canonical/docs/Engineering Guide/04 AI Coding Tool Compatibility.mdmarkdown3.6 KB
canonical/docs/Engineering Guide/05 MCP Setup.mdmarkdown6.6 KB
canonical/docs/Engineering Guide/Documentation/01 Principles.mdmarkdown15.3 KB
canonical/docs/Engineering Guide/Documentation/02 Structure.mdmarkdown3.8 KB
canonical/docs/Engineering Guide/Documentation/03 HLD Intent.mdmarkdown8.1 KB
canonical/docs/Engineering Guide/Documentation/04 LLD Intent.mdmarkdown9.7 KB
canonical/docs/Engineering Guide/Documentation/05 NFR Intent.mdmarkdown6.0 KB
canonical/docs/Engineering Guide/Documentation/07 Terminology.mdmarkdown1.4 KB
canonical/docs/Engineering Guide/Lifecycles/00 Overview.mdmarkdown5.8 KB
canonical/docs/Engineering Guide/Lifecycles/01 Dev Lifecycle.mdmarkdown19.9 KB
canonical/docs/Engineering Guide/Lifecycles/02 Design Lifecycle.mdmarkdown29.4 KB
canonical/docs/Engineering Guide/Lifecycles/03 Evolve Lifecycle.mdmarkdown7.0 KB
canonical/docs/Engineering Guide/Lifecycles/04 Architecture Lifecycle.mdmarkdown3.6 KB
canonical/docs/Engineering Guide/Lifecycles/05 Documents Flow.mdmarkdown9.5 KB
canonical/manifest.jsonconfig1.6 KB
canonical/mcp.jsonconfig23 B
canonical/root-instructions/INTERFACE.mdmarkdown3.3 KB
canonical/settings.jsonconfig332 B
canonical/skills/design/INTENT.mdmarkdown28.6 KB
canonical/skills/design/TEMPLATE.mdmarkdown19.0 KB
canonical/skills/design/interfaces/architecture.mdmarkdown2.8 KB
canonical/skills/design/interfaces/contract.mdmarkdown7.4 KB
canonical/skills/design/interfaces/design.mdmarkdown2.3 KB
canonical/skills/design/interfaces/efforts.mdmarkdown2.5 KB
canonical/skills/design/interfaces/stack.mdmarkdown1.6 KB
canonical/skills/design/patterns/announce-progress.mdmarkdown997 B
canonical/skills/design/patterns/approval-intelligent.mdmarkdown1.5 KB
canonical/skills/design/patterns/approval-sign-off.mdmarkdown2.4 KB
canonical/skills/design/patterns/context-resolution.mdmarkdown6.6 KB
canonical/skills/design/patterns/design-architect-review.mdmarkdown2.4 KB
canonical/skills/design/patterns/design-oq-triage.mdmarkdown3.8 KB
canonical/skills/design/patterns/design-quality-gate.mdmarkdown1.4 KB
canonical/skills/design/patterns/do-report-commit.mdmarkdown1.2 KB
canonical/skills/design/patterns/docs-writer-authoring.mdmarkdown3.6 KB
canonical/skills/design/patterns/metrics.mdmarkdown11.9 KB
canonical/skills/design/patterns/multi-decision-split.mdmarkdown3.6 KB
canonical/skills/design/patterns/phase-sign-off.mdmarkdown2.4 KB
canonical/skills/design/patterns/satellite-review.mdmarkdown1.5 KB
canonical/skills/design/patterns/session-continuity.mdmarkdown827 B
canonical/skills/design/patterns/task-tracking.mdmarkdown779 B
canonical/skills/design/patterns/waf-review.mdmarkdown4.2 KB
canonical/skills/design/patterns/write-confirm.mdmarkdown963 B
canonical/skills/design/references/00-decision-router.mdmarkdown3.8 KB
canonical/skills/design/references/00-router.mdmarkdown4.6 KB
canonical/skills/design/references/01-context-gathering.mdmarkdown8.1 KB
canonical/skills/design/references/02-ceremony.mdmarkdown4.6 KB
canonical/skills/design/references/03-frame.mdmarkdown6.7 KB
canonical/skills/design/references/04-research.mdmarkdown8.1 KB
canonical/skills/design/references/05-evaluate.mdmarkdown9.0 KB
canonical/skills/design/references/06-solution.mdmarkdown13.7 KB
canonical/skills/design/references/07-review-gate.mdmarkdown4.1 KB
canonical/skills/design/references/08-address-feedback.mdmarkdown8.0 KB
canonical/skills/design/references/09-publish.mdmarkdown8.9 KB
canonical/skills/design/references/10-completion.mdmarkdown7.4 KB
canonical/skills/design/scripts/constants.mjsscript2.0 KB
canonical/skills/design/scripts/design-metrics.mjsscript35.4 KB
canonical/skills/design/scripts/design-metrics.test.mjsscript12.0 KB
canonical/skills/design/scripts/utils.mjsscript3.1 KB
canonical/skills/design/templates/evaluate.mdmarkdown1.4 KB
canonical/skills/design/templates/frame.mdmarkdown2.6 KB
canonical/skills/design/templates/report.mdmarkdown4.8 KB
canonical/skills/design/templates/research.mdmarkdown2.4 KB
canonical/skills/design/templates/stat.jsonconfig1.7 KB
canonical/skills/design/templates/stat.schema.jsonconfig17.1 KB
canonical/skills/dev/INTENT.mdmarkdown15.9 KB
canonical/skills/dev/TEMPLATE.mdmarkdown9.0 KB
canonical/skills/dev/interfaces/intent.mdmarkdown2.6 KB
canonical/skills/dev/patterns/announce-progress.mdmarkdown1.1 KB
canonical/skills/dev/patterns/approval-intelligent.mdmarkdown1.5 KB
canonical/skills/dev/patterns/approval-sign-off.mdmarkdown1.9 KB
canonical/skills/dev/patterns/do-report-commit.mdmarkdown888 B
canonical/skills/dev/patterns/metrics.mdmarkdown17.7 KB
canonical/skills/dev/patterns/phase-sign-off.mdmarkdown2.2 KB
canonical/skills/dev/patterns/review-gate.mdmarkdown3.6 KB
canonical/skills/dev/patterns/satellite-review.mdmarkdown3.1 KB
canonical/skills/dev/patterns/session-continuity.mdmarkdown797 B
canonical/skills/dev/patterns/task-tracking.mdmarkdown766 B
canonical/skills/dev/patterns/write-confirm.mdmarkdown615 B
canonical/skills/dev/references/00-router.mdmarkdown2.2 KB
canonical/skills/dev/references/01-context-gathering.mdmarkdown10.3 KB
canonical/skills/dev/references/02-ceremony.mdmarkdown4.5 KB
canonical/skills/dev/references/03-plan.mdmarkdown14.2 KB
canonical/skills/dev/references/04-implement.mdmarkdown11.7 KB
canonical/skills/dev/references/05-test.mdmarkdown7.8 KB
canonical/skills/dev/references/06-document.mdmarkdown11.7 KB
canonical/skills/dev/references/07-completion.mdmarkdown6.3 KB
canonical/skills/dev/scripts/constants.mjsscript3.2 KB
canonical/skills/dev/scripts/quality.mjsscript9.1 KB
canonical/skills/dev/scripts/quality.test.mjsscript6.6 KB
canonical/skills/dev/scripts/timing.mjsscript38.1 KB
canonical/skills/dev/scripts/timing.test.mjsscript21.0 KB
canonical/skills/dev/scripts/utils.mjsscript3.1 KB
canonical/skills/dev/templates/plan.mdmarkdown3.3 KB
canonical/skills/dev/templates/report.mdmarkdown6.4 KB
canonical/skills/dev/templates/stat.jsonconfig1.4 KB
canonical/skills/dev/templates/stat.schema.jsonconfig29.3 KB
canonical/skills/evolve/INTENT.mdmarkdown1.6 KB
canonical/skills/evolve/TEMPLATE.mdmarkdown1.3 KB
canonical/skills/evolve/interfaces/improvement.mdmarkdown1.2 KB
canonical/skills/evolve/interfaces/reflection.mdmarkdown353 B
canonical/skills/evolve/interfaces/validation.mdmarkdown653 B
canonical/skills/evolve/patterns/task-tracking.mdmarkdown787 B
canonical/skills/evolve/references/00-router.mdmarkdown1.1 KB
canonical/skills/evolve/references/01-reflect.mdmarkdown805 B
canonical/skills/evolve/references/02-triage.mdmarkdown2.6 KB
canonical/skills/evolve/references/03-draft.mdmarkdown1.2 KB
canonical/skills/evolve/references/04-validate.mdmarkdown1.5 KB
canonical/skills/evolve/references/05-adopt.mdmarkdown1.5 KB
canonical/skills/war/INTENT.mdmarkdown4.5 KB
canonical/skills/war/TEMPLATE.mdmarkdown1.8 KB
canonical/skills/war/patterns/present-and-save.mdmarkdown1.0 KB
canonical/skills/war/patterns/scope-resolution.mdmarkdown830 B
canonical/skills/war/references/01-design.mdmarkdown3.4 KB
canonical/skills/war/references/02-implementation.mdmarkdown3.8 KB
canonical/skills/war/templates/design-report.mdmarkdown869 B
canonical/skills/war/templates/implementation-report.mdmarkdown1.8 KB
canonical/skills/where-we-are/INTENT.mdmarkdown3.3 KB
canonical/skills/where-we-are/TEMPLATE.mdmarkdown6.3 KB
canonical/skills/where-we-are/report-template.mdmarkdown2.0 KB
canonical/skills/x-ray/INTENT.mdmarkdown2.4 KB
canonical/skills/x-ray/TEMPLATE.mdmarkdown10.5 KB
implementation-harness.mdmarkdown1.4 KB
package.jsonmanifest696 B
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/CHANGELOG.md.patchother1.2 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/README.md.patchother1.9 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/SKILL.md.patchother2.5 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/agents/docs-writer/INTENT.md.patchother1.4 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/docs/.og/cli.test.mjs.patchother846 B
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/docs/Engineering Guide/04 AI Coding Tool Compatibility.md.patchother3.4 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/docs/Engineering Guide/05 MCP Setup.md.patchother5.2 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/manifest.json.patchother662 B
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/settings.json.patchother150 B
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/canonical/skills/design/INTENT.md.patchother19.4 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/patterns/skill-authoring.md.patchother692 B
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/host-capabilities.md.patchother1.2 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/launch/01-launch.md.patchother1.1 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/launch/01a-launch-plan.md.patchother1.6 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/launch/01b-launch-install.md.patchother7.3 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/launch/02-launch-questions.md.patchother5.2 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/launch/08-provider-launch.md.patchother3.2 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/patch/04-patch-harvest.md.patchother2.6 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/patch/05-patch-apply.md.patchother3.0 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/references/patch/06-patch-state.md.patchother7.1 KB
patch/20261105T160045Z-3.3.0-copilot-provider-6630df3d-f6bf-4651-8732-8048942ad1fe/diffs/scripts/lib/agent-format.mjs.patchother2.2 KB

canonical/skills/dev/INTENT.md

View on GitHub
---
skill: dev
output: {{provider:skills_root}}/dev/SKILL.md
companion_templates:
  - scripts/constants.mjs
  - scripts/utils.mjs
  - scripts/quality.mjs
  - scripts/quality.test.mjs
  - patterns/approval-sign-off.md
  - patterns/approval-intelligent.md
  - patterns/phase-sign-off.md
  - scripts/timing.mjs
  - scripts/timing.test.mjs
  - templates/stat.schema.json
  - templates/stat.json
  - patterns/metrics.md
  - interfaces/intent.md
  - templates/plan.md
  - templates/report.md
  - patterns/review-gate.md
  - patterns/session-continuity.md
  - patterns/write-confirm.md
  - patterns/announce-progress.md
  - patterns/do-report-commit.md
  - patterns/satellite-review.md
  - patterns/task-tracking.md
  - references/00-router.md
  - references/01-context-gathering.md
  - references/02-ceremony.md
  - references/03-plan.md
  - references/04-implement.md
  - references/05-test.md
  - references/06-document.md
  - references/07-completion.md
---

## Purpose

The full dev lifecycle in one skill: Context Gathering → Ceremony → Plan →
Implement → Test → Document → Completion. Routes to each stage reference in order
(or directly to one stage, on request). One real stop per phase, at its end
(patterns/phase-sign-off.md); steps inside a phase use intelligent checkpoints.
Completion is its own stage so "done" is never ambiguous: archive, final metrics,
commit and PR text, tracker/tech-debt offers, a clear closing message. Replaces the former separate `dev-plan`, `dev-implement`, `dev-test`,
`dev-document` skills — those stages now live under this one skill's `references/`.
Context Gathering captures the ticket's intent once (from the tracker, any approved
design, and the developer's own words) as `0-intent.md`, before any branch or plan
work. Separation of concerns across the three documents: `0-intent.md` answers
what/for whom/where the edges are and follows an interface (`interfaces/intent.md`),
free in shape; `1-plan.md` answers how and follows a strict template with a
`## Solution` section (approach + target-state Mermaid diagram when wiring matters);
`2-report.md` records what happened. Nothing is repeated between them; they link.

## Substitutions

| Placeholder                  | Source                            | Notes                                                                                                                                                                                                                                                                                                                                                                                                             |
| ---------------------------- | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{{COMMIT_FORMAT}}`          | Q7 — commit message format        | Not a literal token: a rendering rule. Every proposed commit message in `TEMPLATE.md` and `references/*.md` (`docs({ticket-lowercase}): …`, `feat(scope): …`, the Completion commit) is rewritten to the project's format from Q7, e.g. `<TICKET> <summary>`. Shipped default is Conventional Commits `<type>(<scope>): <what>`. The Conventions article states the format once; the skill must not contradict it |
| `{{BRANCH_FORMAT}}`          | Q7 — branch naming                | Rendering rule, same as above, for every proposed branch name (`feat/{ticket-or-local-id}-{slug}` in Ceremony Step 2), e.g. `feature/<ticket>-<short-desc>`. Shipped default is `<type>/<ticket>-<slug>`                                                                                                                                                                                                          |
| `{{PROJECT_KEY}}`            | Q5 — ticket prefix                | e.g. `AIFD`. Replaces every occurrence of `ND` used as a tracker project key                                                                                                                                                                                                                                                                                                                                      |
| `{{BUILD_UNIT_LABEL}}`       | Q2/Q3 — detected monorepo tool    | The generic noun this project's tooling uses for one buildable/testable unit, e.g. `NX project` for an NX monorepo, `package` for a Turborepo/pnpm/Lerna workspace, `module` (or just the app's name) for a single non-monorepo app. Used in `references/03-plan.md` and `references/04-implement.md` wherever the plan/commit-scope guidance refers to one discrete unit — not just in command strings.          |
| `{{NX_BUILD_CMD}}`           | Test stage — detected NX projects | Full `yarn nx run-many -t build -p {projects}` command. Detect project names from `project.json` files under `apps/`. Example: `yarn nx run-many -t build -p bff web`                                                                                                                                                                                                                                             |
| `{{NX_DB_MIGRATE_CMD}}`      | Test stage — detected DB project  | Full `yarn nx run {db-project}:migrate` command. Detect DB project name from `apps/` structure. Example: `yarn nx run db:migrate`                                                                                                                                                                                                                                                                                 |
| `{{INFRA_SYNTH_CMD}}`        | Q — infra tooling                 | Command to synthesize/validate infra. Terraform: `terraform validate`. CDK: `yarn nx run infra:synth`. Pulumi: `pulumi preview`.                                                                                                                                                                                                                                                                                  |
| `{{INFRA_DIFF_CMD}}`         | Q — infra tooling                 | Command to diff/plan infra changes. Terraform: `terraform plan`. CDK: `yarn nx run infra:diff`. Pulumi: `pulumi preview --diff`.                                                                                                                                                                                                                                                                                  |
| `{{DOC_PRINCIPLES_ARTICLE}}` | Q — Doc Principles article path   | e.g. `docs/Engineering Guide/Documentation/01 Principles.md` — read by `@docs-writer`, not by the Document stage                                                                                                                                                                                                                                                                                                  |
| `{{DOC_STRUCTURE_ARTICLE}}`  | Q — Doc Structure article path    | e.g. `docs/Engineering Guide/Documentation/02 Structure.md` — used by Document stage Step 0                                                                                                                                                                                                                                                                                                                       |

Transition IDs are never substituted here — dev only asks `@scrum-master` to
transition a ticket by state name ("In Progress", "Done", …); the tracker agent
resolves the ID from its own definition. Keeping that mapping in one place
(`@scrum-master`) avoids the two skills drifting out of sync.

## Conditionals

- If Q5 is "none" (no issue tracker): remove every tracker-specific reference across `TEMPLATE.md` and all seven `references/*.md` files — Context Gathering Step 2 (fetch tracker context), Ceremony Step 1 (tracker setup), and Completion Step 5's tracker and tech-debt ticket offers. Rewrite the entry route for free-form work without a ticket key. Do not insert the answer `None` or an explanation such as "tracker references removed" into a ticket-prefix placeholder; remove or rewrite the entire dependent sentence/section. Do not leave Jira/Confluence names, tracker credentials, tracker transition steps, tracker task creation, or tracker-only commands.
- If no specialist agents are defined for a layer: replace `references/04-implement.md` and `references/05-test.md`'s delegation logic with "implement/review inline" for that layer
- If no DB layer exists in the project: remove `references/05-test.md` Step 4 (DB migration check), all database start/migrate prompts and commands, and any claim that a local database is required.
- If no install, build, test, or run command is configured: say that the command is not configured and do not invent one. Remove dependent onboarding steps that cannot run; retain the applicable verification guidance.
- If not an NX monorepo (Q3/Q2 detection): replace the NX commands in `references/05-test.md` with the project's actual build/test commands, and resolve `{{BUILD_UNIT_LABEL}}` to the detected tool's own term (or the single app's name if there is no monorepo tool at all) rather than leaving "NX project" as the default wording

## Verify checklist

- [ ] TEMPLATE.md starts with `---` frontmatter containing `name:` (skill name) and `description:` (trigger conditions for this skill)
- [ ] With a tracker: routes cover the seven named stages (including `complete`) and bare-ticket full chain; ticket matching uses the confirmed project prefix, with no unresolved project token or example `ND` prefix.
- [ ] Without a tracker: the seven named stages and free-form full-chain entry work without ticket keys, tracker credentials, transitions, or `@scrum-master`. Resolve ambiguous stage words in context.
- [ ] The router's entry check is the only fresh-vs-resume decision, for full-chain and direct-stage entry alike; no stage reference carries its own Step 0. It reuses the matching story folder/report (by ticket key, or by description and recorded path without a tracker, asking only if several match). Single-stage entry does not restart the chain.
- [ ] No literal "Jira" wording in `TEMPLATE.md` or any `references/*.md` — tracker activity is named generically and delegated to `@scrum-master`, never described with tracker-specific vocabulary or transition IDs
- [ ] TEMPLATE.md only delegates — no implementation logic, no step details (those live in `references/`)
- [ ] `references/01-context-gathering.md` creates the story folder, the `2-report.md` skeleton and metrics (Step 2b, before the heavy reading) and `0-intent.md` — no other stage creates these; `stage start --stage context` runs before Step 3
- [ ] `references/04-implement.md` applies `patterns/task-tracking.md` for per-step tasks, in addition to the stage-level task the router creates
- [ ] Every Phase-row string across `TEMPLATE.md` and `references/*.md` lists all seven stages in order (`🎯 Context · 🚀 Ceremony · 📋 Plan · 🔨 Implement · 🧪 Test · 📝 Document · 🏁 Completion`) with consistent status icons
- [ ] Story and archive folder names are ASCII only: `docs/Stories/[{TICKET}] {name}` and `docs/Stories/archive/[{TICKET}] {name}`, no emoji or em dash anywhere in a folder name
- [ ] Every `patterns/*.md` and `templates/*.md` reference across `TEMPLATE.md` and `references/*.md` uses the subfolder path (`patterns/X.md`, `templates/Y.md`), never the old flat `pattern-X.md` / `X-template.md` form
- [ ] Story folder globs use `*{TICKET}*` wildcard, never `[{TICKET}]*`, everywhere they appear
- [ ] `0-intent.md` is written against `interfaces/intent.md` (questions, not headings); `1-plan.md` uses `templates/plan.md` with `## Solution`, `## Acceptance Criteria`, `## Steps` and links the intent instead of repeating problem/scope

- [ ] Metrics CLI and schema companions are installed verbatim; run `node --test <dev-skill>/scripts/*.test.mjs` to verify them

- [ ] The dev metrics CLI and its own `scripts/constants.mjs` / `scripts/utils.mjs` work when installed alone; its standalone-install test passes

- [ ] One Review Findings ledger uses stable IDs across reviews; no separate live findings tables.
- [ ] HLD-only deviation audit routes routine LLD updates directly to Documentation.
- [ ] Every proposed commit message and branch name in `TEMPLATE.md` and `references/*.md` follows the project's own format from Q7 (no Conventional-Commits or `feat/` default left where the project uses another style); the Conventions article and the skill agree
- [ ] One stop per phase: Context Step 5, Ceremony Step 2, Plan Step 5, Implement Step 4, Test Step 5, Document Step 6 are
      phase sign-offs and still stop unconditionally; Completion Step 4 is one combined ask.
      No other unconditional stops exist. Ceremony Step 1, Test Steps 2–4, Document Steps 2–5, Plan Step 4
      rework and Implement Step 3 step checkpoint are intelligent
      checkpoints. Omitted tracker branches must not be restored to satisfy this list.
- [ ] Every phase sign-off step carries its own `wait start` + **Stop and wait** line and records a `<Stage> sign-off` acceptance check; `scripts/timing.mjs` refuses `stage complete` without one in the current attempt (covered by its tests)
- [ ] Every stage reference names marking the stage's native task `in_progress` and then
      `stage start` as its first actions, and ends with the same three steps — Sign-off (rework
      if any) → Report (`2-report.md`, metrics `report`) → Commit (proposed, developer runs it,
      verified in Git, then `stage complete`; Implement by step/block) — with every stop preceded
      by `report` + `wait start`. Context Gathering is the one exception: it ends with Report →
      Close (`stage complete`, no commit); its files ride in Ceremony's first commit after checkout.
- [ ] Quality summary preserves unknown counts and distinguishes failed runs from cases.
- [ ] Closure requires evidence for terminal resolutions; full-flow tracker completion has one owner.

- [ ] Plan Step 3 does not use the host's native planning mode (the stage writes files and
      delegates); the Plan phase sign-off at Step 5 is its only gate.
- [ ] Plan Step 1 writes tests by default when the project has a test setup for the touched layers (type chosen from the work, existing framework only); skipping it requires a stated reason in the plan. Its verification is "suite runs, new cases red as expected", recorded as a passed self-sourced acceptance check so the metrics gate can close the step.

## Component-agent routing

Derive implementation components from repository structure, build configuration,
architecture and confirmed ownership. Instantiate `agents/layer/TEMPLATE.md` with
its INTENT separately for each component that needs a specialist. Names, scope,
toolchain and responsibilities come from evidence, not a fixed frontend/backend/data
list. Record `Component | Owned paths | Agent | Responsibilities` in the selected
root instruction file's Agents table; both providers share the same ownership map.
Implementation and Test resolve owners from that table and the installed role definitions.
Do not add category-specific agent placeholders to skills. No matching owner means
explicit inline handling; ambiguous ownership must be resolved before delegation.

- [ ] All referenced component specialists exist and their scopes match the root Agents table. During bootstrap Stage A, record this as a cross-stage check owned by B/C; resolve it when those outputs exist, before final verification.
- [ ] No fixed component categories or guessed specialist names drive implementation/review routing.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall