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/where-we-are/report-template.md
View on GitHub# Delivery Gap Report — {{VERSION}}
_Generated: {{YYYY-MM-DD}}_
---
## Summary
{{2–3 sentence narrative: overall delivery posture, dominant gap type, most critical gaps}}
---
## Gap Matrix
| Container | Designed (HLD) | Implemented (code) | Documented (LLD) | Gap |
| ------------------------------------------------------- | -------------- | ------------------ | ---------------- | --- |
| {{one row per container discovered from HLD in Step 2}} | | | | |
**Gap key:**
- **LLD missing** — designed and implemented but not documented → documentation debt
- **Not yet built** — designed but no implementation exists → delivery debt
- **In progress** — partial implementation → in-flight
- **Design debt** — HLD has significant open questions or TBD sections
- **—** — fully covered across all three dimensions
---
## Delivery Debt
Containers designed but not yet implemented (or only stubbed):
{{list — one entry per container, describe what is missing and why it matters}}
---
## Documentation Debt
Containers implemented but with empty or partial LLD coverage:
{{list — one entry per container, describe what would be most valuable to capture}}
---
## Design Debt
HLD containers with significant open questions or TBD sections:
{{list — one entry per container, describe what needs to be resolved and what is blocked on it}}
---
## Recommended Next Actions
| Priority | Action | Command |
| -------- | ---------- | ------------------------------------------------------------------------------------ |
| P1 | {{action}} | `{{provider:invoke:dev}} document <TICKET>` or `{{provider:invoke:design}} <TICKET>` |
| P2 | {{action}} | |
| P3 | {{action}} | |
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 |