From sth-harness
Codex, Pi, Copilot CLI, and AGY entry point for installing ai-harness, adding feature specs, and implementing the next pending spec without Claude slash commands.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sth-harness:sth-harnessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user asks Codex, Pi, Copilot CLI, or Google Antigravity
Use this skill when the user asks Codex, Pi, Copilot CLI, or Google Antigravity
CLI (agy) to initialize the ai-harness, add a new feature spec, or implement
the next pending spec.
skills/sth-harness/SKILL.md.../../scripts/ from this skill directory.../../template/ai-harness/.CLAUDE_PLUGIN_ROOT may also point at the plugin root, but
do not require it in Codex, Pi, Copilot CLI, or AGY.init, initialize, bootstrap, or "install the harness" -> run Init.add spec, new spec, or "create a feature" -> run Add Spec.implement next spec, implement, next spec, or "continue harness work"
-> run Implement Next Spec.Bootstrap the AI harness into the user's repository, then create the first
feature. Use the harness-interview skill for all question-asking.
./ai-harness/ already exists, stop. Tell the user the harness is already
installed and suggest adding a spec instead. Do not overwrite.scripts/copy-harness.sh with the current repository as its argument.
Confirm exit 0 and that ./ai-harness/START-HERE.md now exists. On non-zero
exit, report the script's stderr and stop../ai-harness/context/project.md via the harness-interview skill:
detect and link existing docs, assess whether the README is rich enough,
interview for gaps, set the app type, and offer to seed a README with the
bundled scripts/seed-readme.sh only when no README exists. Replace every
<!-- CUSTOMIZE --> in project.md, including inline comments in examples;
link, do not duplicate.harness-tool-linking skill.
For Codex, run the bundled scripts/link-codex.sh; for Pi, run the bundled
scripts/link-pi.sh; for Copilot CLI, run the bundled
scripts/link-copilot-cli.sh; for AGY, run the bundled
scripts/link-agy.sh. Each writes AGENTS.md so the tool reads AGENTS.md
-> ai-harness/START-HERE.md../ai-harness/specs/global-spec-info.md and
./ai-harness/specs/global-state-info.md for exact fields and legal
vocabulary.ai-harness/specs/_template/ to ai-harness/specs/<feature>/.spec.md and state.md from the answers, using the legal vocabulary
verbatim. Set phase, overall: todo, and a concrete next../ai-harness/context/project.md, the first feature's
spec.md and state.md, root adapter files, and a seeded README if one was
created). If any actionable <!-- CUSTOMIZE --> placeholder remains, keep
interviewing or fill from known facts until it is gone. Do not count
documentation-only occurrences that merely explain the marker itself, such as
copied harness docs like ai-harness/README.md,
ai-harness/context/testing.md, ai-harness/context/architecture.md, or
decision records.Ask one question at a time. Never invent requirements; ask or record an open question. The harness reference files are the source of truth.
Add a new feature to an already-initialized harness. Use the harness-interview
skill for question-asking.
./ai-harness/ does not exist, stop. Tell the user to initialize the
harness first../ai-harness/specs/global-spec-info.md and
./ai-harness/specs/global-state-info.md for fields and legal vocabulary.ai-harness/specs/<feature>/ already exists, stop and ask for a different
name.ai-harness/specs/_template/ to ai-harness/specs/<feature>/.spec.md and state.md from the answers, using legal vocabulary
verbatim. Set phase to the furthest-completed phase, overall: todo, and a
concrete next.Write only inside ai-harness/specs/<feature>/ on the current branch. Do not run
git commands.
Implement the next pending feature following the harness. Use the
harness-implement skill for the implementation loop.
./ai-harness/ does not exist, stop. Tell the user to initialize the
harness first.ai-harness/specs/*/state.md, skipping _template. Read each
header: feature, phase, and overall state. A spec is pending unless its
overall state is done or cancelled.blocked > review > doing > todo.
To break a tie at the top, read only the tied specs' spec.md and prefer the
one whose highest-priority requirement is greatest: must > should >
could. If still tied, present the tied specs and let the user pick.harness-implement skill: act as Session
Loader, then adopt the role for the current phase from ai-harness/roles.md.
Read only that role's section and honor the feature's state.md read budget.doing, follow TDD where practical, keep the domain pure, and update
state.md after each task.state.md before stopping. Report the stop reason and the next action.Read only the chosen feature's folder plus the shared context files needed for the current step. Do not touch other features.
npx claudepluginhub danielemiliogarcia/sth-harness-plugin --plugin sth-harnessGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.