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/02-ceremony.md
View on GitHub# Ceremony stage
Apply `{{provider:skills_root}}/design/patterns/metrics.md`; this stage's metrics
unit is `--stage ceremony`. First action: `stage start --stage ceremony`.
Resume detection and stage tracking live in `{{provider:skills_root}}/design/SKILL.md`.
This stage is the official start of work: assign and transition the ticket via
`@scrum-master`, and get onto the right branch. It reads and writes no framing
content โ that's Frame's job.
Two stops in this stage: the branch checkout in Step 2, which is the phase
sign-off, and the commit in Step 4. Step 1 is an intelligent checkpoint
(`patterns/approval-intelligent.md`).
> ๐ **Session continuity:** apply `{{provider:skills_root}}/design/patterns/session-continuity.md`.
## Step 1 โ Tracker transition _(skip if no ticket number detected)_
Invoke `@scrum-master` to read the ticket's current assignee and status first โ
never assume it's untouched.
This is an intelligent-approval checkpoint (`patterns/approval-intelligent.md`).
Auto-approval conditions: unassigned (or already assigned to the authenticated
user); in a pre-work status (Backlog/To Do/Selected); and In Progress is the
confirmed, unambiguous next workflow transition.
All conditions met โ auto-approve: invoke `@scrum-master`:
> "Start {TICKET}: assign to the authenticated user and transition to In Progress."
Announce what was done (ticket, prior status, new status), add a one-line note
in `design/Report.md` that ceremony auto-assigned the ticket, and continue to
Step 2 without asking first.
Any condition fails or is uncertain (already assigned elsewhere, already past In
Progress, or the next status isn't obvious) โ this is a sign-off gate
(`patterns/approval-sign-off.md`): present to the developer:
> "{{PROJECT_KEY}}-XX is currently `{assignee}` / `{status}`. I'll assign it to you and
> move it to **In Progress**. Confirm? (**yes** / **skip**)"
Use existing tracker authorization if already given, otherwise ask once. **Stop
and wait for confirmation.** If confirmed, invoke `@scrum-master` with the same
start instruction above.
## Step 2 โ Sign-off: the feature branch
Apply `patterns/phase-sign-off.md`. If you are already on the feature branch for
this ticket, say so; that is a fact from Git, not a decision, and the sign-off
is just "we're on `{branch}`, continuing". Otherwise the branch is where all the
work lands, so the developer confirms it. Checkout is their operation; never run
`git checkout`/`git switch` yourself. Propose the exact command:
> "Ticket is {assigned / transitioned / unchanged}. Please check out the feature
> branch for this work:
>
> ```bash
> git checkout -b docs/{ticket-lowercase}-{slug}
> ```
>
> or tell me a different name. Let me know once you're on it."
If the worktree has unrelated changes, say so in the same message instead of
proposing a switch that would conflict. Never discard or stash the developer's
changes. On the reply, check the branch with Git before continuing; if it is
not the one agreed, say so and wait again. Then record the acceptance check
(`--name "Ceremony sign-off"`, `--source developer`, evidence: the branch name
they confirmed); without it `stage complete` is refused. If you were already on
the branch, record it with `--source self` and the branch name; that is the one
sign-off the developer gave implicitly, by being there.
## Step 3 โ Report
Set the `Branch` row to the actual branch and the `Phase` row to
`๐ฏ Context Gathering โ
ยท ๐ Ceremony โ
ยท ๐ Frame ๐ ยท ๐ Research โณ ยท ๐ Evaluate โณ ยท ๐ฆ Solution โณ ยท ๐ Review โณ ยท ๐ฌ Address Feedback โณ ยท ๐ค Publish โณ ยท ๐ Completion โณ`.
Add a one-line note if the ticket was auto-assigned. Then metrics `report`.
## Step 4 โ Commit
The lifecycle's first commit, on the branch just checked out. Propose
`docs({TICKET}): gather context and record branch` covering
`{{DESIGN_STORIES_ROOT}}[{TICKET}] {name}/design/` (Report.md, stat.json) and this stage's
row. If the story folder was already committed earlier (a resumed design), propose
only `docs({TICKET}): record branch and tracker state`.
This is a manual-operation sign-off (`patterns/approval-sign-off.md`) โ the
developer runs the commit, never you. `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. Then `stage complete --stage ceremony`. Tell the developer which
branch you're on and continue to Frame for full-flow entry.
๐ Re-read `{{provider:skills_root}}/design/SKILL.md` and resume the router from the next stage (Frame).
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 |