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/patterns/do-report-commit.md
View on GitHub# Do → Report → Commit
Applies at the end of every design stage, after `patterns/phase-sign-off.md`'s
sign-off is approved. Report and Commit are routine — no sign-off, no wait, no
stop on Report; Commit is its own stop because it is a manual operation.
## Steps
1. **Do** — the sign-off is already approved; the artifact is final.
2. **Report** — update `design/Report.md`: Phase tracker (current phase `✅`,
next phase `🔄`), append an Efforts row (date, phase, one-line note). Then
metrics `report`.
3. **Commit** — present the suggested commit message. This is a manual-operation
sign-off (`patterns/approval-sign-off.md`): the developer runs it, you wait.
`wait start --reason user_input`. **Stop and wait.** On the reply, check
`git log`/`git status`: the commit exists and the worktree holds nothing from
this phase. If not, say what is missing and wait again. Only then
`stage complete`.
After the commit is confirmed, announce the outcome and continue straight into
the next phase — no separate "ready to continue?" question.
## Invariant
`design/Report.md` must reflect the completed phase before any commit is
presented. It is the recovery point — the next session reads it to know where
to resume.
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: 470k | 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 |