{ "markdown": "

\n \"Strikethroo:\n

\n\n

\n Spec-driven development optimized for time-to-merge, not time-to-first-draft.
\n You review the plan, where a correction costs a sentence — not the diff, where it costs a review cycle.\n

\n\n

\n \"npm\n \"tests\"\n \"node\n \"MIT\n

\n\n

\n Why Strikethroo  · \n Workflow  · \n Customization  · \n Visualizations  · \n FAQ\n

\n\n## Why Strikethroo?\n\nMost spec-driven tools optimize the input: better spec in, better code out, human catches the rest at the end. Strikethroo assumes the agent is an unreliable narrator of its own work -- including a second agent asked to review the first -- and that the scarce resource is your attention, not tokens.\n\n\n\n\n\n\n\n\n\n\n
\n\n\"\"\n\n### You review the plan, not the diff\n\nCorrecting a plan costs a sentence. Correcting the same misunderstanding in a diff costs a review cycle, a rework cycle, and a re-review. An explicit approval gate puts your careful read where it is worth the most, and one question is asked at a time so it never gets skim-answered.\n\n\n\n\"\"\n\n### Guarantees are compiled, not requested\n\nA rule in Markdown is a request; a rule in TypeScript is a guarantee. Hooks and templates are yours to edit. The certification rule -- an uncertified review is never reported as a clean one -- is compiled and cannot be loosened by editing a hook.\n\n
\n\n\"\"\n\n### Nobody marks their own homework\n\nThe optional review gate runs on a *different* harness than the one that wrote the code -- the current harness is structurally excluded from the candidate set, not merely deprioritized. The reviewer detects and never fixes; findings are reported for you to act on.\n\n\n\n\"\"\n\n### Bends to your conventions\n\nPlain-Markdown hooks fire at eleven points across the workflow; inject your test commands, standards, and domain rules so every plan, task, and run inherits them. No plugins, no code.\n\n
\n\n**Speed, measured honestly.** The industry clock starts at the prompt and stops when code appears. The clock that pays your salary stops when the code is **merged** -- and on that clock, generation is a rounding error next to the review rounds a fast-but-wrong draft costs you. Strikethroo is built against the second clock. That is not quality traded for speed; on that clock they are the same number.\n\nRead the full thesis, with the file-by-file claims to verify it yourself: **[Why Strikethroo](https://strikethroo.canpicasoft.com/why.html)**.\n\nAlso true, and less interesting: no API keys (runs on the subscription you already pay for), harness-agnostic Agent Skills (one `SKILL.md` on any harness supporting the format), and clean per-agent context at every step.\n\n## Adapts to every codebase\n\nEvery codebase has its own conventions, and Strikethroo bends to them instead of imposing its own. Three plain-Markdown surfaces -- no plugins, no code:\n\n[![Strikethroo's customizable spec-driven workflow, showing where the hooks fire: PRE_PLAN, POST_PLAN, POST_TASK_GENERATION_ALL, PRE_TASK_ASSIGNMENT, and POST_EXECUTION](docs/assets/strikethroo-customization.png)](docs/assets/strikethroo-customization.png)\n\n### \"\" Hooks\n\nFire at eleven points across the workflow (before planning, after each phase, on errors, and more). Drop in your test commands, coding standards, and domain rules; every plan, task, and execution run inherits them.\n\n### \"\" Templates\n\nDefine the shape of plans and tasks -- add your own sections and checklists.\n\n### \"\" Project context\n\nOne file of domain knowledge every step reads.\n\nHooks, templates, and a project-context file are all plain Markdown -- nothing to compile, no plugin API to learn. See the [Customization Guide](https://strikethroo.canpicasoft.com/customization.html) for examples.\n\n## Quick Start\n\n```bash\n# 1. Bootstrap the shared workspace\nnpx strikethroo init --harnesses claude\n\n# 2. Install the workflow skills\nnpx skills add e0ipso/strikethroo\n```\n\nOn re-init, `--harnesses` is optional — Strikethroo reuses the saved selection in `.ai/strikethroo/.init-metadata.json`. Workspaces initialized before that field existed must pass `--harnesses` once.\n\n**Already set up?** Refresh the workspace and update installed workflow skills in one step:\n\n```bash\nnpx strikethroo@latest update\n```\n\nExit 0 requires both the workspace refresh and the skills installer to succeed. If the installer fails after a successful refresh, the refreshed workspace is kept; re-run `update` or the installer command it reports. Start a fresh agent session after updating — a running session may still follow previous skill instructions. Old skill copies cannot show update notices until you run `update` once.\n\nRequires Node.js 22+ and an assistant that supports the Agent Skills format.\n\n## Profiles: a tailored setup in one step\n\nA strikethroo profile packages a complete workspace configuration -- hooks, templates, project context -- so `init --profile ` starts from a setup tuned for your stack instead of the shipped defaults, and `export profile` packages yours to share. See [Strikethroo profiles](https://strikethroo.canpicasoft.com/customization.html#strikethroo-profiles) in the Customization Guide.\n\n## In your coding assistant\n\n```mermaid\nflowchart LR\n A[Work Order] --> B[Plan]\n B --> C{Review}\n C -->|Edit| B\n C -->|Approve| G[\"Execute
(generates tasks)\"]\n G --> H[\"Code Review
(optional)\"]\n H -->|Fix| G\n H -->|Pass| J[Done]\n```\n\n**Two commands.** Read the plan, approve it, run it:\n\n| Step | Command | Output |\n|-------------|---------------------------------|---------------------------------------------------------|\n| **Plan** | `/st-create-plan ` | `.ai/strikethroo/plans/64--auth/plan-64--auth.md` |\n| **Execute** | `/st-execute-blueprint 64` | Task blueprint, then working code, one commit per phase |\n| **Review** | Automatic (optional) | Findings validated against schema; report-only |\n\n`st-execute-blueprint` decomposes the plan into atomic tasks and builds the dependency-mapped blueprint itself when one does not exist yet. Run `/st-generate-tasks 64` on its own only when you want to inspect or hand-tune the blueprint before execution starts.\n\nYour review lands on the plan, before any code exists -- that is where a correction costs a sentence. Each step runs with clean context: the planning agent sees only the work order, and each execution sub-agent receives only its specific task. After execution, an optional automated review gate runs once on a discovered second harness, critiques the cumulative diff, and reports schema-validated findings for you to act on.\n\nSee the [Workflow Guide](https://strikethroo.canpicasoft.com/workflow.html) for the full step-by-step with advanced patterns. Once a plan exists, visualize its plans, tasks, and dependency graph in [Visualizations](https://strikethroo.canpicasoft.com/visualizations.html).\n\n## Visualize the data\nStrikethroo comes with an optional **web application** to help you visualize your plans, tasks, and progress. No installation necessary, just execute the following command in a project using Strikethroo:\n\n```shell\nnpx strikethroo serve\n```\n\nThis will open a web page that will help you navigate your plans and their tasks, present or archived.\n\n## Check the workspace\n\n```shell\nnpx strikethroo validate\n```\n\nReads your workspace and reports internal inconsistencies -- missing or malformed plan and task frontmatter, dependencies pointing at tasks that do not exist, dependency cycles, blueprint phases and task files that disagree, duplicate ids. It only reads: nothing is written or fixed for you. Every finding is an error, so the command exits non-zero as soon as it reports one, which makes it usable as a CI step. Add `--json` for a machine-readable report on stdout, or `--workspace ` to point it at a workspace other than the one discovered from the current directory.\n\n| Plans board | Plan detail page | Archive |\n|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|\n| [![img](docs/assets/plans-board.png)](docs/assets/plans-board.png) | [![img](docs/assets/plan-detail-graph.png)](docs/assets/plan-detail-graph.png) | [![img](docs/assets/archive-all.png)](docs/assets/archive-all.png) |\n\n## Optional Code Review Gate\n\nAfter blueprint execution, an optional automated code review gate runs once when a second harness is discovered. The reviewer critiques the cumulative diff against the plan's requirements and emits findings validated against a schema. The gate reports; it does not decide -- there are no severity or confidence floors, and nothing is applied automatically. You read the findings and choose what to act on.\n\n**To disable:** Edit `.ai/strikethroo/config/hooks/CODE_REVIEW.md` to empty or delete it. The gate skips cleanly with a note in the execution summary.\n\n**Important:** A green review gate is not a correctness guarantee. The gate reduces exposure to the same class of error a human PR approval reduces, and leaves the same class of error behind. See [Customization](https://strikethroo.canpicasoft.com/customization.html) for limitations and configuration.\n\n## Documentation\n\n- [Why Strikethroo](https://strikethroo.canpicasoft.com/why.html) -- The design thesis, the trade-offs stated plainly, and how to verify the claims\n- [Workflow Guide](https://strikethroo.canpicasoft.com/workflow.html) -- Step-by-step workflow with visual guides\n- [Customization Guide](https://strikethroo.canpicasoft.com/customization.html) -- Hooks, templates, project context, and code review configuration\n- [Reference](https://strikethroo.canpicasoft.com/reference.html) -- Glossary and CLI reference\n- [FAQ](https://strikethroo.canpicasoft.com/faq.html) -- Answers to common questions\n- [Visualizations](https://strikethroo.canpicasoft.com/visualizations.html) -- See plans, tasks, and the dependency graph\n- [Migrating from 1.x](https://strikethroo.canpicasoft.com/migration.html) -- Upgrade from slash commands to Agent Skills\n", "bytes": 12405, "sha": "e5081dc6aadc6486ac8c10e590a8fc2b7a5c02cafbe02edf9829c67a3254f86b", "repo_slug": "e0ipso/strikethroo", "fonte": "repo", "truncated": false, "api": "https://agentalog.com/api/listings/okf_e0ipso_strikethroo_ai_kenkeep_nodes_inde_a6489baa/readme" }