| name | implement |
| description | Build a shaped Gradient context packet into docs, YAML profiles, JSON Schema,
synthetic fixtures, or harness files. Trigger: /implement, /build.
|
| argument-hint | [context-packet-path|task] |
/implement
Implementation in this repo is currently contract work, not application code.
Make surgical changes to docs, schemas, profiles, examples, or harness files.
Rules
- State assumptions before changing files.
- Strengthen one named lifecycle stage.
- Keep the public-safe boundary intact.
- Do not add deployment-specific logic or customer-private context.
- Do not invent app tests, CI, or deploy commands.
- Prefer deletion and schema clarity over broad prose expansion.
TDD Equivalent
When editing schemas or fixtures:
- Write or update the synthetic fixture first when useful.
- Update the schema or docs.
- Validate when a validator exists.
- Mark missing validation command as
UNVERIFIED.
For pure docs, acceptance criteria replace tests: the changed doc must cite the
authoritative source and not contradict docs/architecture.md,
docs/module-contracts.md, or docs/decision-log.md.
Lifecycle Gap
This repo now has backlog.d as the Work adapter v0, but no closure
detector beyond the tracer-bullet fixture. Until a detector exists, preserve
work references manually and mark closure mechanics unverified.
Gate
The load-bearing ship gate is ./scripts/validate.sh, plus reviewer
judgment for lifecycle semantics in docs/architecture.md and
docs/module-contracts.md when docs change.
Branch Reference
Use branch names that can later map to work references when a tracker exists:
docs/<short-slug>, schema/<short-slug>, or harness/<short-slug>.
