DataArt/artisyn-implementation-harness / skills/implementation-harness
implementation-harness
FlaggedInstall 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.
canonical/skills/design/references/00-router.md
View on GitHub# Stage reference router
Resume detection, how approvals work, the Phase tracker, and stage tasks live in
[SKILL.md](../SKILL.md). Each row below is loaded only when its stage runs.
| Stage | Reference | Produces |
| ----------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Context Gathering | [01-context-gathering.md](01-context-gathering.md) | Ticket/local ID resolved, tracker context fetched, track/subfolder resolved; story folder + `design/Report.md` created |
| Ceremony | [02-ceremony.md](02-ceremony.md) | Tracker transition + branch confirmed |
| Frame | [03-frame.md](03-frame.md) | `design/00 Frame.md` |
| Research | [04-research.md](04-research.md) | `design/01 Research.md` (or per-decision variants), Assumptions recorded |
| Evaluate | [05-evaluate.md](05-evaluate.md) | `design/02 Evaluate.md`, closing WAF block in `design/Report.md` |
| Solution | [06-solution.md](06-solution.md) | Selected solution artifacts recorded in `design/Report.md`; WAF review via `patterns/waf-review.md` |
| Review Gate | [07-review-gate.md](07-review-gate.md) | Draft MR opened, `design/Report.md` Gate recorded, parked for approval |
| Address Feedback | [08-address-feedback.md](08-address-feedback.md) | Confirms the approval outcome; if concerns, reiteration applied and re-approval recorded; if declined, routes straight to Completion; if approved outright, skips itself and routes to Publish |
| Publish | [09-publish.md](09-publish.md) | Permanent docs updated — skipped entirely for a declined design |
| Completion | [10-completion.md](10-completion.md) | Implementation tickets published, story archived (`approved/` or `declined/`), tracker synced, commit + PR handed over |
Context Gathering and Ceremony are separate stages, mirroring the `dev` skill:
Context Gathering only reads and resolves (ticket, tracker, track/subfolder);
Ceremony is the only stage that mutates the tracker or checks out a branch.
Frame then writes the framing content using what Context Gathering resolved.
Design-lifecycle artifacts live under `{{DESIGN_STORIES_ROOT}}` — active at
`{{DESIGN_STORIES_ROOT}}[{TICKET}] {name}/`, archived at
`{{DESIGN_STORIES_ROOT}}approved/[{TICKET}] {name}/` or
`{{DESIGN_STORIES_ROOT}}declined/[{TICKET}] {name}/`. `{{DESIGN_STORIES_ROOT}}`
is `docs/Stories/design/` for a Project design or `docs/Stories/product-design/`
for a Product design — resolved once, in Context Gathering (see
`patterns/context-resolution.md`), the same way `{{DESIGN_DOCS_ROOT}}` is.
Shared protocols used across these stages live in [patterns/](../patterns/). Lifecycle
templates live in [templates/](../templates/); solution artifacts use the adaptive
contracts in [interfaces/](../interfaces/).
[00-decision-router.md](00-decision-router.md) is not a stage — it has no row
above and no entry in the Phase tracker. It's the shared loop mechanics
Research, Evaluate, and Solution each apply when Frame confirmed two or more
decisions: which steps loop per decision, and which close once regardless of
how many.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |