Strikethroo
Strikethroo transforms complex development requests into structured, validated implementations through plain text files and Agent Skills. No API keys. No additional tools. Works within your existing AI subscription and across any harness that supports the Agent Skills format.
Quick Start
# 1. Bootstrap the shared workspace
npx strikethroo init --harnesses claude
# 2. Install the workflow skills
npx skills add e0ipso/strikethroo
See Getting Started for prerequisites and directory structure.
How It Works
flowchart LR
A[Work Order] --> B[Plan]
B --> C{Review}
C -->|Edit| B
C -->|Approve| D[Tasks]
D --> E{Review}
E -->|Edit| D
E -->|Approve| F[Execute]
F --> G[Done]
style A fill:#ffebee
style B fill:#e3f2fd
style D fill:#f3e5f5
style F fill:#e8f5e8
style G fill:#c8e6c9
Three steps, each delivered as an Agent Skill that loads when you describe what you need:
| Step | You say | Skill | Output |
|---|---|---|---|
| Plan | “Plan user auth with JWT” | st-create-plan | .ai/strikethroo/plans/01--auth/plan-01--auth.md |
| Tasks | “Decompose plan 1” | st-generate-tasks | .ai/strikethroo/plans/01--auth/tasks/*.md |
| Execute | “Execute the blueprint for plan 1” | st-execute-blueprint | Working code, one commit per phase |
Human review gates between steps catch scope creep before any code is written. Each step runs with clean context – the planning agent sees only the work order, the task agent sees only the approved plan, and each execution sub-agent receives only its specific task.
See the Workflow Guide for the full step-by-step with advanced patterns.
Documentation
- Getting Started – Install and run your first workflow
- Workflow Guide – Step-by-step workflow with visual guides
- Customization Guide – Hooks, templates, and project context
- Reference – Glossary, CLI reference, FAQ
- Migrating from 1.x – Upgrade from slash commands to Agent Skills