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/Documentation/07 Terminology.md
View on GitHub# Terminology
_The approved term for each project concept that has more than one plausible name._
---
## Why
A concept named three different ways across three documents reads as three concepts until a reader checks. This registry fixes one approved term per concept so `docs-writer` and every design artifact use the same word every time.
See `01 Principles.md`'s "One term per concept" rule in Manner — this file is that rule's data.
---
## How this fills up
- **At launch**, if this file has no rows yet, the orchestrator scans existing code identifiers, README/doc nouns, and confirmed Q&A domain language for recurring project-specific terms and seeds an initial set. Skipped if rows already exist — launch never overwrites an established registry.
- **During `/design`**, Solution Step 2 proposes a row for any domain term the solution coins that isn't here yet; `docs-writer` appends it as part of writing `solution/Architecture.md`.
- **Anywhere else**, add a row by hand the moment two documents start using different words for the same thing.
A term stays out of this table if it's standard English, a well-known industry term (HTTP, Lambda, CDK), or used exactly once — the registry is for project-specific concepts at risk of drifting, not a full glossary.
---
## Registry
| Term | Approved form | Forbidden synonyms | Definition | Introduced in |
| ---- | ------------- | ------------------ | ---------- | ------------- |
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 |