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/INTENT.md
View on GitHub---
skill: where-we-are
output: {{provider:skills_root}}/where-we-are/SKILL.md
companion_templates:
- report-template.md
---
## Purpose
Produces a delivery gap report: what has been designed in Target Architecture (HLD) vs documented in System Architecture (LLD) vs implemented in the codebase. Delegates code scanning to `@architect`.
## Substitutions
| Placeholder | Source | Notes |
| -------------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{{LLD_FOLDER_STRUCTURE}}` | Stage 1b — detected from repo | The `docs/System Architecture (LLD)/` subfolder structure. Detect from existing `docs/System Architecture (LLD)/` folder or use generic container names from Q3. Do not hardcode ncfc-specific folders (Canonical, Compute, Synthetic, Serving, Data, Infrastructure) |
| `{{CODE_SCAN_TARGET}}` | Q2/Q3 — detected monorepo tool and layout | A phrase describing where code lives, matched to the project's actual layout — e.g. "the NX monorepo under `apps/` and `libs/`" for an NX monorepo, "the Turborepo monorepo under `apps/`" for a Turborepo project with no `libs/`, "the codebase" for a single non-monorepo app. Shared with `war`'s `references/02-implementation.md`. |
| `{{BUILD_UNIT_LABEL}}` | Q2/Q3 — detected monorepo tool | Same placeholder as `dev`'s INTENT — the generic noun for one buildable unit (`NX project`, `package`, `module`, or the single app's name). |
## Conditionals
None.
## Verify checklist
- [ ] TEMPLATE.md starts with `---` frontmatter containing `name:` (skill name) and `description:` (trigger conditions for this skill)
- [ ] Step 1 reads HLD README to find active version — not hardcoded
- [ ] Step 3 shows the actual LLD folder structure detected from the project (not ncfc's Canonical/Compute/etc.)
- [ ] `{{CODE_SCAN_TARGET}}` and `{{BUILD_UNIT_LABEL}}` in Step 4 are resolved to the project's actual detected monorepo tool and directory layout — never left hardcoded as "NX monorepo" / "`apps/` and `libs/`" for a project that uses a different tool or layout
- [ ] Step 4 `@architect` prompt is bounded: "Return a structured list. Do not write files. Do not make changes."
- [ ] Step 5 gap matrix rows are populated from HLD containers discovered in Step 2, not hardcoded
- [ ] Step 7 uses `report-template.md` from same skill folder
- [ ] Output path: `docs/System Architecture (LLD)/where-we-are/{YYYY-MM-DD}-gap-report.md`
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 |