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/docs/Engineering Guide/Lifecycles/00 Overview.md
View on GitHub# Implementation Harness — Lifecycle Overview
_The four lifecycles, how they interact, and when to use each one._
Commands are written with a leading `{{SKILL_PREFIX}}` — your provider's skill-invocation
prefix. See `04 AI Coding Tool Compatibility.md` for the full provider mapping.
---
## The four lifecycles
| Lifecycle | Orchestrator | Phases |
| ---------------- | ------------------------ | ---------------------------------------------------------------------------------------------------- |
| **Dev** | `{{SKILL_PREFIX}}dev` | Context → Ceremony → Plan → Implement → Test → Document → Completion |
| **Design** | `{{SKILL_PREFIX}}design` | Frame → Research → Evaluate → Solution → Review Gate → Address Feedback → Publish |
| **Skill** | — (no orchestrator) | Reflect → Triage → Draft → Validate → Adopt |
| **Architecture** | — (standalone commands) | `{{SKILL_PREFIX}}where-we-are` · `{{SKILL_PREFIX}}war design` · `{{SKILL_PREFIX}}war implementation` |
Each orchestrator runs its phases in order. Dev stops once per phase, at its end, for a sign-off; inside a phase it runs its own checks and keeps going. Other lifecycles retain their own review gates. Individual phase commands (`{{SKILL_PREFIX}}dev plan`, `{{SKILL_PREFIX}}design frame`, etc.) run the requested stage or support resuming mid-flow.
---
## When to use which lifecycle
| Situation | Use |
| --------------------------------------------- | ------------------------------------------------------------- |
| Any ticket — feature, bug fix, chore | Dev lifecycle always |
| Ticket is large, novel, or crosses containers | Design lifecycle first, then Dev |
| Something surprised you during a ticket | Evolve lifecycle (Reflect) |
| Observed harness friction | Evolve lifecycle (Triage) |
| End of sprint / before planning | Architecture lifecycle (`{{SKILL_PREFIX}}where-we-are`) |
| After major HLD changes | Architecture lifecycle (`{{SKILL_PREFIX}}war design`) |
| Before a major release | Architecture lifecycle (`{{SKILL_PREFIX}}war implementation`) |
**Design is optional.** Small, well-understood changes within a single container that introduce no new integrations or architecture decisions — skip Design, go straight to Dev.
---
## Cross-lifecycle invariants
- Follow each lifecycle's approval contract. Dev reuses existing authorization across routine phase transitions; unresolved material decisions still require human input.
- No code is written until the plan is approved and the architecture audit passes.
- Documentation is mandatory, and a ticket is complete only when `{{SKILL_PREFIX}}dev complete` has archived the story and said so.
- Architecture deviations approved at plan time are tracked through to the Document phase.
- Reflections are not optional ceremony — they are how conventions accumulate.
→ See `Engineering Guide/03 Engineer Role.md` for how engineers and AI divide responsibility within these lifecycles.
---
## Lifecycle interactions
```mermaid
flowchart TB
TICKET(["🎫 Ticket"]):::ticket
subgraph DESIGN [" 🎨 Design lifecycle (optional) "]
direction LR
D1["Frame\nproblem + ECs"]:::design --> D2["Research\noptions via {{DESIGN_ARCHITECT_AGENT}}"]:::design --> D3["Evaluate\nmatrix + recommend"]:::design --> D4["Solution\ncertainty artifacts"]:::design --> D5["Publish\nMR → docs → tickets"]:::design
end
subgraph DEV [" 🔨 Dev lifecycle "]
direction LR
V1["Plan\n+ arch audit"]:::dev --> V2["Implement\nstep-by-step"]:::dev --> V3["Test\n+ PR review"]:::dev --> V4["Document\n+ deviations"]:::dev --> V5["Completion\narchive + PR"]:::dev
end
subgraph SKILL [" 💡 Evolve lifecycle "]
direction TB
S1["Reflect"]:::skill --> S2["Triage"]:::skill --> S3["Promote"]:::skill
end
WAR["🏛️ WAR Audit\n{{SKILL_PREFIX}}war design · {{SKILL_PREFIX}}war implementation\nIs the architecture sound?"]:::war
WWA["📊 Where We Are\n{{SKILL_PREFIX}}where-we-are\nDesigned vs implemented vs documented"]:::wwa
TICKET -->|"large / novel"| DESIGN
DESIGN -->|"Publish creates\nimpl tickets"| DEV
TICKET -->|"routine"| DEV
DESIGN -->|"feeds"| WAR
DEV -->|"feeds"| WWA
DEV -->|"surprises"| S1
S3 -->|"updated skills"| DEV
TICKET2(["🎫 New tickets"]):::ticket
WAR -.->|"gap tickets"| TICKET2
WWA -.->|"gap tickets"| TICKET2
classDef ticket fill:#2C3E50,stroke:#1A252F,color:#fff
classDef design fill:#8E44AD,stroke:#6C3483,color:#fff
classDef dev fill:#1A6B3C,stroke:#14532d,color:#fff
classDef skill fill:#D97706,stroke:#B45309,color:#fff
classDef war fill:#1D4ED8,stroke:#1e3a8a,color:#fff
classDef wwa fill:#0E7490,stroke:#0c4a6e,color:#fff
```
---
→ `01 Dev Lifecycle.md` — Context → Ceremony → Plan → Implement → Test → Document → Completion
→ `02 Design Lifecycle.md` — Frame → Research → Evaluate → Solution → Review Gate → Address Feedback → Publish
→ `03 Evolve Lifecycle.md` — Reflect → Triage → Draft → Validate → Adopt
→ `04 Architecture Lifecycle.md` — `{{SKILL_PREFIX}}where-we-are` · `{{SKILL_PREFIX}}war design` · `{{SKILL_PREFIX}}war implementation`
→ `05 Documents Flow.md` — how docs are born, graduate, and reach their permanent home
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 |