← ClaudeAtlas

story-cyclelisted

Use when the user wants to implement a single story or deliver a backlog item.
joris887/exosuit · ★ 4 · AI & Automation · score 74
Install: claude install-skill joris887/exosuit
______________________________________________________________________ ## story-cycle Delivering story: **$ARGUMENTS** **Skill metrics:** Emit a start event to the activity log: ```bash echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"story-cycle\",\"story\":\"$ARGUMENTS\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl ``` **Progress tracking:** At the start, create a task list for phase tracking: 1. "Phase 0+1: Decompose intent, research, plan" — activeForm: "Planning..." 2. "Phase 2: Context transition + readiness gate" — activeForm: "Preparing..." — blockedBy: [1] 3. "Phase 3: Implement by story type" — activeForm: "Implementing..." — blockedBy: [2] 4. "Phase 4: Verify, quality gates, commit" — activeForm: "Verifying..." — blockedBy: [3] At each phase boundary, mark the current task completed and the next task in_progress. ## Process Flow (authoritative — prose below is supporting detail) ``` START → Phase 0: Intent Decomposition (identify ALL deliverables, mark uncertainties) → Size Classification: → [TRIVIAL: single-file, <10 lines, no behavioral change] → Phase 3-lite: Make change → Run tests → Abbreviated self-review → Commit → DONE → [SMALL: single-file, <50 lines, clear AC] → Lightweight Phase 1 (skip 1f-1g) → Phase 2 → Phase 3 → Phase 4 → DONE → [STANDARD: everything else] → Phase 1: Plan Mode (research, identify type, write plan with WHAT/HOW separation) → Phase 1c.5: Online