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/references/01-context-gathering.md

View on GitHub
# Context Gathering stage

Apply `{{provider:skills_root}}/dev/patterns/metrics.md`; this stage's metrics unit is
`--stage context`. Metrics start in Step 2b below, not at the end of the stage.

Routing and stage tracking live in `{{provider:skills_root}}/dev/SKILL.md`. This stage
captures what the ticket actually means, once: from the tracker, any approved design,
and the developer's own words. It writes that down as `0-intent.md` before any branch
or plan work starts. Read-only apart from the story folder, the report skeleton and
the intent file.

One stop in this stage: the sign-off in Step 5 on the written intent. There is no
commit here; the story folder is committed by Ceremony Step 4, after the branch
checkout, so the lifecycle's first commit lands on the feature branch. The sign-off
(`patterns/phase-sign-off.md`). It covers both the gathered context and the intent
written from it; gaps and conflicts are asked there, as open questions in the file,
not earlier. Everything planned later derives from that file.

> ๐Ÿ” **After context compaction:** re-read this file and run metrics `recover`
> before recording anything (`patterns/session-continuity.md`). Fresh vs. resume was
> already decided by the router's entry check; do not redo completed work.

## Step 1 โ€” Parse the input

Detect the input shape:

- **Ticket only** โ€” `{{PROJECT_KEY}}-42`
- **Free-form only** โ€” no ticket number (e.g. `hey lets build CI pipelines. Thoughts: 1 2 3`)
- **Mixed** โ€” ticket number followed by free-form text

A ticket number matches `{{PROJECT_KEY}}-\d+`. If none is found, reuse an existing
matching `DEV-YYYYMMDD-XXXX` story ID when there is one; otherwise generate a
collision-checked `DEV-YYYYMMDD-XXXX` local ID before creating files.

Extract:

- **ticket** โ€” `{{PROJECT_KEY}}-\d+` if present, otherwise the local ID
- **problem** โ€” what to build or fix (may be empty for ticket-only)
- **thoughts** โ€” the developer's initial ideas (may be empty)
- **context** โ€” file paths, URLs, doc references

## Step 2 โ€” Fetch tracker context _(skip if free-form only)_

Invoke `@scrum-master`:

> "Fetch {TICKET}: return summary, description, acceptance criteria, linked {{PROJECT_KEY}} tickets, and any Confluence page URLs."

Then fetch each linked Confluence page and pull out the relevant content
(requirements, specs, design notes). Note constraints from other `{{PROJECT_KEY}}-*`
tickets the description references. This is a read only: do not assign or
transition the ticket here, that is Ceremony's job.

**Merging with developer input (mixed case):** the developer's problem and thoughts
win over tracker content if they conflict. Tracker/Confluence is background and
acceptance criteria; developer input is the primary intent.

**If `@scrum-master` reports a tracker error** (timeout, auth, not found): do not
block. Continue with developer input only, note `Tracker unavailable` in the intent's
sources, and ask for the missing pieces:

> "I couldn't fetch {{PROJECT_KEY}}-XX from the tracker. To continue, please paste:
>
> - **Summary** โ€” one-line ticket title
> - **Description** โ€” what needs to be built
> - **Acceptance criteria** โ€” how to know it's done (if any)"

**Stop and wait** for that before Step 2b. Record `wait start --reason user_input`
only if metrics already exist (they won't on a fresh ticket; that is fine).

## Step 2b โ€” Create the story folder, report skeleton and start metrics

Do this now, before the heavy reading. The story name is known at this point: the
ticket summary, or a short slug of the free-form problem.

- Glob for `docs/Stories/*{TICKET}*/` (use `*{TICKET}*` wildcard โ€” never `[{TICKET}]*`)
- If a design folder already exists (e.g. `[{TICKET}] {name}/`), create `impl/` inside it
- Otherwise create `docs/Stories/[{TICKET}] {name}/impl/`

The folder name is **stable for the life of the ticket**. Never rename it. Phase
state lives in the `Phase` row of `2-report.md`, not in the folder name. Use only
ASCII characters in the name: no emoji, no em dash. Some scanners cannot index such
folders.

Create `impl/2-report.md` from `{{provider:skills_root}}/dev/templates/report.md`:

- `{TICKET}` and `<Short Title>` โ€” from the ticket / intent title
- Header table โ€” fill Ticket and Author (`git config user.name`); Branch is `โ€”` until
  Ceremony sets it; PR `โ€”`; Status `๐Ÿ”„ In Progress`; Phase
  `๐ŸŽฏ Context ๐Ÿ”„ ยท ๐Ÿš€ Ceremony โณ ยท ๐Ÿ“‹ Plan โณ ยท ๐Ÿ”จ Implement โณ ยท ๐Ÿงช Test โณ ยท ๐Ÿ“ Document โณ ยท ๐Ÿ Completion โณ`
- Leave the Progress table empty; Plan fills it

Then mark the Context stage's native task `in_progress`
(`patterns/task-tracking.md`), and initialise metrics and start the stage, reusing
the same `git config user.name` value:

```sh
node {{provider:skills_root}}/dev/scripts/timing.mjs init --dir "$IMPL_DIR" --ticket "$TICKET" --author "$AUTHOR"
node {{provider:skills_root}}/dev/scripts/timing.mjs stage start --dir "$IMPL_DIR" --stage context
```

Everything from here on is recorded as Context work.

## Step 3 โ€” Check for approved design

- Glob for `docs/Stories/design/approved/*{TICKET}*/solution/Architecture.md`
  and `docs/Stories/product-design/approved/*{TICKET}*/solution/Architecture.md`
  (use `*{TICKET}*` wildcard) โ€” an approved design lives under an `approved/`
  subfolder of one of the two design-lifecycle roots (`design/` for a Project
  design, `product-design/` for a Product design), never directly under the
  root (still active) or its `declined/` subfolder
- If found, read the story's `design/Report.md` and the paths in its
  `selected_artifacts`. Those approved files are the spec. Do not assume a fixed
  Architecture/Design/Stack/Efforts set.

If found, tell the developer:

> "Found approved design for `{TICKET}` โ€” reading `solution/Architecture.md` and the selected solution artifacts as the source of truth for intent and planning."

The solution files are the primary spec for the intent. Developer input and tracker ACs
supplement; they do not override the solution. If nothing is found, continue; intent
comes from the tracker and the developer alone.

## Step 3.5 โ€” Verify uncertain platform/framework conventions

If the intent depends on a specific external platform, service or framework
convention (required file layout, config keys, manifest fields, API shape) and you
are not sure about it, fetch the official docs first: `WebFetch` the vendor page if
the URL is known, or `WebSearch` to find it. Skip this for things you know well
(a standard `package.json`, common language idioms). This is for cases where getting
it wrong is plausible, not a mandate to fetch docs for everything.

Cite what you consulted (the URL) in the intent's sources.

## Step 3.6 โ€” Identify the HLD container(s) in scope

Read `docs/Target Architecture (HLD)/README.md` to find the active version and its
container index, then name the container(s) this ticket falls under. This is a
quick identification, not the deep read; that happens in Plan Step 1. The point is
to catch an obvious boundary mismatch (scope that belongs to a different container,
or spans containers unexpectedly) while it is still cheap to fix.

Include the container(s) in the intent. If the scope does not map cleanly,
say so rather than silently picking one.

## Step 3.7 โ€” Query the operational graph for related docs

Before searching by hand, attempt
`node docs/.og/cli.mjs query --related-to <doc> --dir .` (or `search --term <text>`)
against `docs/.og/docs-operational-graph.sqlite` to surface docs already related to this ticket's
scope. This is a required (not best-effort) fallback: when the graph is missing,
stale (see `references/reindex-graph.md`'s Staleness check), or the call errors, fall back to grep/glob over `docs/` for the same
information. Either way, never let this block the stage.

## Step 4 โ€” Write 0-intent.md

Write `impl/0-intent.md` following `{{provider:skills_root}}/dev/interfaces/intent.md`.
That file is an interface, not a template: it lists the questions the intent must
answer (problem, what better looks like, who is affected, out of scope, constraints,
open questions) and leaves the shape to you. Write in the originator's own words,
link every source, keep it short. No steps, no acceptance criteria, no solution;
those belong to the plan.

Write it even when the context is incomplete. Anything you could not settle goes in
as an open question, with what you found so far: a missing description or
acceptance criteria, a conflict between the developer's words and the tracker, a
boundary concern from Step 3.6, a design change the developer hinted at. The
developer answers those in the sign-off, against the written file, not against a
chat summary.

## Step 5 โ€” Sign-off

Apply `patterns/phase-sign-off.md`. The developer confirms the written
intent, not a chat summary (`patterns/write-confirm.md`). Present:

> "Intent written to `docs/Stories/[{TICKET}] {name}/impl/0-intent.md`. In short:
>
> - **Problem**: `<one line>`
> - **Better looks like**: `<one line>`
> - **Affected**: `<users / apps / container(s)>`
> - **Out of scope**: `<one line or 'nothing stated'>`
> - **Constraints**: `<one line or 'none'>`
> - **Open questions**: `<list or 'none'>`
> - **Sources**: `<ticket, pages, design, your message>`
>
> Is this the right intent? Anything missing, wrong, or out of scope before I
> plan against it? {If there are open questions: "I need your answer on the open
> questions above before Plan."}"

`report`, then `wait start --reason approval --detail "Awaiting context sign-off"`.
**Stop and wait.** No reply, no next step. On approval, record the acceptance check
(`--name "Context sign-off"`, `--source developer`, their words as evidence); without
it `stage complete` is refused.

Rework: update `0-intent.md` with the answers and present again. Once approved, the
intent is confirmed; only the open questions may be appended later.

## Step 6 โ€” Report

Set the `Phase` row to
`๐ŸŽฏ Context โœ… ยท ๐Ÿš€ Ceremony ๐Ÿ”„ ยท ๐Ÿ“‹ Plan โณ ยท ๐Ÿ”จ Implement โณ ยท ๐Ÿงช Test โณ ยท ๐Ÿ“ Document โณ ยท ๐Ÿ Completion โณ`,
then metrics `report`.

## Step 7 โ€” Close

No commit in this stage. `stage complete --stage context`. Continue to Ceremony for a
full-flow request. For direct entry stop here and say that the story folder is
uncommitted on purpose until `{{provider:invoke:dev}} ceremony {TICKET}` checks out the
branch and proposes the first commit.

๐Ÿ” Re-read `{{provider:skills_root}}/dev/SKILL.md` and resume the router from the next stage (Ceremony).
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