Menu
Guided interactive tour of the framework. Walks through your first sprint from zero to shipped PR.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/joris887/exosuit --skill quickstartThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Based on SOC occupation classification
| name | quickstart |
| version | 1.0.0 |
| description | Guided interactive tour of the framework. Walks through your first sprint from zero to shipped PR. |
| trigger | manual |
| depends-on | [] |
| references | [] |
| disable-model-invocation | true |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash |
Welcome to the Exosuit framework. This guided tour walks you through your first complete sprint, from planning to shipped PR.
Present the framework's core concept:
### How This Framework Works
The framework adds structure to AI-assisted development:
**Three Layers:**
1. **Enforcement:** hooks that auto-format code, scan for secrets, block dangerous commands (automatic)
2. **Workflow:** skills (slash commands) that guide your development process (you invoke these)
3. **Documentation:** knowledge base that compounds across sessions (generated and updated)
**The Core Loop:**
/sprint-start → /story-cycle (repeat) → /sprint-end
Each `/story-cycle` takes a story through: plan → approve → implement (TDD) → verify → commit.
Run a quick health check:
# Check if bootstrap has been run
if [ -f "docs/architecture/ARCHITECTURE.md" ] && ! grep -q "<!-- " docs/architecture/ARCHITECTURE.md 2>/dev/null; then
echo "READY: Bootstrap complete"
else
echo "NOT READY: Run /bootstrap first"
fi
Present options using AskUserQuestion:
Walk through each step with explanation:
**What happens:** Creates a clean feature branch from main.
Try it: `/sprint-start`
This will:
- Check for open PRs (merge or note them)
- Verify you're on the default branch and up to date
- Run tests to confirm a green baseline
- Create a `sprint-N` branch
**Behind the scenes:** The SessionStart hook checked your environment when you opened Claude Code.
Wait for user to run /sprint-start, then continue.
**What happens:** Delivers a single story with TDD and quality gates.
Try it: `/story-cycle "add a health check endpoint"` (or any small feature)
This will:
1. **Phase 0:** Decompose your request, classify size and risk
2. **Phase 1:** Research the codebase, write a plan, ask for your approval
3. **Phase 2:** Score confidence (must be ≥85 to proceed)
4. **Phase 3:** Implement using TDD (tests first, then code)
5. **Phase 4:** Self-review, quality gates, commit
**Behind the scenes:** Every edit triggers auto-formatting and secrets scanning.
The testing.md rule auto-loads when test files are edited.
Wait for user to complete a story-cycle, then continue.
**What happens:** Ships your work via a PR with quality gates.
Try it: `/sprint-end`
This will:
- Run lint, typecheck, and test suite
- Verify test count didn't decrease
- Run quality agents (code-quality, test-validator, security-audit)
- Check ground rules compliance
- Create a PR with structured description
- Wait for CI, then squash-merge to main
**Behind the scenes:** Quality agents run as parallel sub-processes with confidence scoring.
Only findings ≥80 confidence are reported.
**What happens:** Captures your session state for continuity.
Try it: `/handoff`
This creates a structured session file in docs/sessions/ that /continue reads next time.
Alternatively, just stop; the Stop hook auto-saves your git state.
Present the full skill table from CLAUDE.md organized by workflow stage.
Walk through what happens on each event:
### You're Ready
**Essential skills to know:**
- `/story-cycle`: your daily driver for delivering stories
- `/continue`: resume work from a previous session
- `/debug-session`: when something breaks
- `/doctor`: when the framework seems off
**When you need help:**
- `/help-me "I want to..."`: find the right skill for any task
**Weekly rhythm:**
- Monday-Thursday: `/sprint-start` → `/story-cycle` (repeat) → `/sprint-end`
- Friday: `/weekly-maintenance` → `/retrospective`