by rsmdt
The Agentic Startup - A collection of Claude Code commands, skills, and agents.
# Add to your Claude Code skills
git clone https://github.com/rsmdt/the-startupNew in v3: Agent Teams (experimental) β enable multi-agent collaboration where specialized agents coordinate and work together on complex tasks. The installer now offers to configure this automatically.
The Agentic Startup is a multi-agent AI framework that makes Claude Code work like a startup team. Create comprehensive specifications before coding, then execute with parallel specialist agents β expert developers, architects, and engineers working together to turn your ideas into shipped code.
10 slash commands across 3 phases. Specify first, then build with confidence.
Key Features:
No comments yet. Be the first to share your thoughts!
Requirements: Claude Code v2.0+ with marketplace support
curl -fsSL https://raw.githubusercontent.com/rsmdt/the-startup/main/install.sh | sh
This installs the core plugins, configures the default output style, and sets up the statusline with a customizable config file.
Start claude and run the following:
# Add The Agentic Startup marketplace
/plugin marketplace add rsmdt/the-startup
/plugin install start@the-startup # Install the Start plugin (core workflows)
/plugin install team@the-startup # (Optional) Install the Team plugin (specialized agents)
After installation:
# (Optional) Create project governance rules
/constitution # Auto-enforced during specify, implement, review
# Switch output styles anytime
/output-style "start:The Startup" # High-energy, fast execution (default)
/output-style "start:The ScaleUp" # Calm confidence, educational
Create a specification and implement it:
# Create a specification
/specify Add user authentication with OAuth support
# Execute the implementation
/implement 001
That's it! You're now using spec-driven development.
The Agentic Startup follows spec-driven development: comprehensive specifications before code, ensuring clarity and reducing rework.
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β SETUP (optional) β
β β
β /constitution βΊ Create project governance rules β
β (auto-enforced in BUILD workflow) β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β BUILD (primary flow) β
β β
β /specify βββββΊ Create specs (PRD + SDD + PLAN) β
β β β³ Constitution checked on SDD β
β βΌ β
β /validate ββββΊ Check quality (3 Cs framework) β
β β β³ Constitution mode available β
β βΌ β
β /implement βββΊ Execute plan phase-by-phase β
β β β³ Constitution + drift enforced β
β βΌ β
β /test ββββββββΊ Run tests, enforce ownership β
β β β³ No "pre-existing" excuses β
β βΌ β
β /review ββββββΊ Multi-agent code review β
β β β³ Constitution compliance checked β
β βΌ β
β /document ββββΊ Generate/sync documentation β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β MAINTAIN (as needed) β
β β
β /analyze βββββΊ Discover patterns & rules β
β β
β /refactor ββββΊ Improve code (preserve behavior) β
β β
β /debug βββββββΊ Fix bugs (root cause analysis) β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
/specify Add real-time notification system with WebSocket support
This creates a specification directory with three documents:
.start/specs/001-notification-system/
βββ requirements.md # What to build and why
βββ solution.md # How to build it technically
βββ plan/ # Executable tasks and phases
βββ README.md # Plan manifest
βββ phase-N.md # Per-phase task files
The spec cycle may take 15-30 minutes. Claude will research your codebase, ask clarifying questions, and produce comprehensive documents. The process naturally involves multiple back-and-forth exchanges.
Large specifications may approach Claude's context window limits. When this happens:
# Start a new conversation and resume where you left off
/specify 001
The resume pattern:
001) instead of a descriptionPro tip: If Claude suggests "you may want to reset context", do it! The quality of output improves with fresh context.
/validate 001
This quality gate checks:
Validation is advisoryβit provides recommendations but doesn't block you.
/implement 001
Claude will:
Large implementations may also need context resets. Simply run /implement 001 again in a fresh conversationβClaude tracks progress in the spec files.
/review
Four parallel specialists review your code:
What do you need to do?
β
ββ Want project-wide guardrails? ββββββββββΊ /constitution
β
ββ Build something new? βββββββββββββββββββΊ /specify
β Then: /validate β /implement
β
ββ Understand existing code? ββββββββββββββΊ /analyze
β ββ Want to improve it? ββββββββββββββββΊ Then: /refactor
β
ββ Something is broken? βββββββββββββββββββΊ /debug
β
ββ Need to run tests? ββββββββββββββββββββΊ /test
β
ββ Code ready for merge? ββββββββββββββββββΊ /review
β
ββ Need documentation? ββββββββββββββββββββΊ /document
β
ββ Check constitution compliance? βββββββββΊ /validate constitution
| Skill | Purpose | When to Use |
|---------|---------|-------------|
| /constitution | Create governance rules | Establish project-wide guardrails |
| /specify | Create specifications | New features, complex changes |
| /implement | Execute plans | After spec is validated |
| /validate | Check quality | Before implementation, after specs |
| /test | Run tests, enforce ownership | After implementation, fixing bugs |
| /review | Multi-agent code review | Before merging PRs |
| /document | Generate documentation | After implementation |
| /analyze | Extract knowledge | Understanding existing code |
| /refactor | Improve code quality | Cleanup without behavior chang