
Gsd 2 Agent Framework
Run the GSD 2 (`gsd-pi`) spec-driven CLI so milestones split into one-window tasks with worktrees, recovery, and cost tracking while you walk away.
Overview
GSD 2 Agent Framework is an agent skill most often used in Build (also Validate, Ship) that runs the gsd-pi spec-driven CLI for autonomous milestone-slice-task coding with worktrees and recovery.
Install
npx skills add https://github.com/aradotso/trending-skills --skill gsd-2-agent-frameworkWhat is this skill?
- Milestone → slice (4–10) → task (1–7) hierarchy with one-context-window iron rule
- CLI (`gsd-pi`) controls harness, worktree isolation, crash recovery, and cost tracking
- STATE.md and DECISIONS.md registers for long-running auto-mode position
- Spec-driven autonomous build instead of LLM self-loop chat
- npm global install; Node 18+; Pi SDK with Claude (Anthropic)
- Milestone typically contains 4–10 slices
- Slice typically contains 1–7 tasks
- Iron rule: one task must fit one context window
Adoption & trust: 1.4k installs on skills.sh; 31 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your implementation spec is too large for one agent session and self-looping chat loses state, blows cost, and leaves messy git history.
Who is it for?
Indie builders with a written spec who want overnight or walk-away autonomous builds using Claude via the Pi SDK and Node CLI.
Skip if: One-off snippet edits, repos without git discipline, or teams that forbid autonomous shell/git changes without human review gates.
When should I use this skill?
Triggers include gsd autonomous agent, spec-driven development, context engineering coding, long running agent task, gsd auto mode, milestone slice task hierarchy, gsd-pi cli agent, autonomous coding agent framework.
What do I get? / Deliverables
GSD 2 executes tasks in isolated context windows with tracked state and decisions so you return to a built project and coherent commits—invoke after your spec or plan is ready.
- `.gsd/STATE.md` and `.gsd/DECISIONS.md` project registers
- Implemented slices with isolated task commits
- Cost and progress tracking from autonomous runs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Autonomous slice execution is where the product actually gets built from an approved spec using agent harness control. GSD controls context windows, git worktrees, and stuck detection—the agent-tooling layer, not a single feature ticket.
Where it fits
Break a product spec into milestones and slices before any autonomous gsd-pi auto-mode run.
Execute one demoable slice as tasks that each fit a single context window with worktree isolation.
Maintain DECISIONS.md and STATE.md so crash recovery resumes the correct task without re-planning from chat.
Treat each completed slice as a vertical demo checkpoint before the next GSD milestone.
How it compares
A spec-driven autonomous harness CLI, not a single prompt skill or an MCP-only integration.
Common Questions / FAQ
Who is gsd-2-agent-framework for?
Solo builders adopting GSD 2 and gsd-pi for long-running, spec-driven autonomous coding with structured milestones and tasks.
When should I use gsd-2-agent-framework?
Use during validate when locking execution structure from a spec, during build for autonomous slice implementation, and during ship when demoable vertical slices need isolated agent runs with recovery.
Is gsd-2-agent-framework safe to install?
Treat gsd-pi as high-trust automation with git and shell access; review the Security Audits panel on this page and run in worktrees with backups before unattended auto-mode.
SKILL.md
READMESKILL.md - Gsd 2 Agent Framework
# GSD 2 — Autonomous Spec-Driven Agent Framework > Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection GSD 2 is a standalone CLI that turns a structured spec into running software autonomously. It controls the agent harness directly — managing fresh context windows per task, git worktree isolation, crash recovery, cost tracking, and stuck detection — rather than relying on LLM self-loops. One command, walk away, come back to a built project with clean git history. --- ## Installation ```bash npm install -g gsd-pi ``` Requires Node.js 18+. Works with Claude (Anthropic) as the underlying model via the Pi SDK. --- ## Core Concepts ### Work Hierarchy ``` Milestone → a shippable version (4–10 slices) Slice → one demoable vertical capability (1–7 tasks) Task → one context-window-sized unit of work ``` **Iron rule:** A task must fit in one context window. If it can't, split it into two tasks. ### Directory Layout ``` project/ ├── .gsd/ │ ├── STATE.md # current auto-mode position │ ├── DECISIONS.md # architecture decisions register │ ├── LOCK # crash recovery lock file │ ├── milestones/ │ │ └── M1/ │ │ ├── slices/ │ │ │ └── S1/ │ │ │ ├── PLAN.md # task breakdown with must-haves │ │ │ ├── RESEARCH.md # codebase/doc scouting output │ │ │ ├── SUMMARY.md # completion summary │ │ │ └── tasks/ │ │ │ └── T1/ │ │ │ ├── PLAN.md │ │ │ └── SUMMARY.md │ └── costs/ │ └── ledger.json # per-unit token/cost tracking ├── ROADMAP.md # milestone/slice structure └── PROJECT.md # project description and goals ``` --- ## Commands ### `/gsd auto` — Primary Autonomous Mode Run the full automation loop. Reads `.gsd/STATE.md`, dispatches each unit in a fresh session, handles recovery, and advances through the entire milestone without intervention. ```bash /gsd auto # or with options: /gsd auto --budget 5.00 # pause if cost exceeds $5 /gsd auto --milestone M1 # run only milestone 1 /gsd auto --dry-run # show dispatch plan without executing ``` ### `/gsd init` — Initialize a Project Scaffold the `.gsd/` directory from a `ROADMAP.md` and optional `PROJECT.md`. ```bash /gsd init ``` Creates initial `STATE.md`, registers milestones and slices from your roadmap, sets up the cost ledger. ### `/gsd status` — Dashboard Shows current position, per-slice costs, token usage, and what's queued next. ```bash /gsd status ``` Output example: ``` Milestone 1: Auth System [3/5 slices complete] ✓ S1: User model + migrations ✓ S2: Password auth endpoints ✓ S3: JWT session management → S4: OAuth integration [PLANNING] S5: Role-based access control Cost: $1.84 / $5.00 budget Tokens: 142k input, 38k output ``` ### `/gsd run` — Single Unit Dispatch Execute one specific unit manually instead of running the full loop. ```bash /gsd run --slice M1/S4 # run research + plan + execute for a slice /gsd run --task M1/S4/T2 # run a single task /gsd run --phase research M1/S4 # run just the research phase /gsd run --phase plan M1/S4 # run just the planning phase ``` ### `/gsd migrate` — Migrate from v1 Import old `.planning/` directories from the original Get Shit Done. ```bash /gsd migrate # migrate current directory /gsd migrate ~/projects/old-project # migrate specific path ``` ### `/gsd costs` — Cost Report Detailed cost breakdown wit