A starter template for building applications with Claude Code using specialized sub-agents for structured development workflows.
This template gives you a team of AI agents that work together to build your application. Instead of one AI doing everything, specialized agents handle different aspects of development:
- Requirements Agent asks clarifying questions to understand what you want
- Architect Agent makes technology and structure decisions
- Designer Agent creates detailed designs before coding starts
- Developer Agent writes the actual code following best practices
- Test Agents plan, write, and run tests to catch bugs
- Documentation Agent creates user and developer docs
The Task Manager coordinates everything, tracking what's done and what's next.
- You describe what you want to build - in plain language
- Requirements Agent interviews you - asks questions to clarify scope, constraints, and priorities
- Architect makes decisions - chooses technologies, defines structure, documents rationale
- Designer creates blueprints - detailed designs with diagrams before any code is written
- Developer implements - writes code following the designs and project conventions
- Tests are written and run - catches bugs early, routes failures to the right agent to fix
- Documentation is generated - user guides and developer docs
- Structured requirements document following ISO/IEC/IEEE 29148 standards
- Architecture Decision Records (ADRs) explaining why choices were made
- Design documents with Mermaid UML diagrams
- Clean, tested code following language-specific conventions
- Comprehensive tests (unit, integration, E2E)
- Documentation for users and developers
It depends on complexity. A simple feature might complete in one session. A full application takes multiple sessions - use continue to resume where you left off.
GitHub Web UI:
- Click "Use this template" → "Create a new repository"
- Name it and create
- Clone locally
Or GitHub CLI:
gh repo create my-project --template osok/claude-code-startup --clone
cd my-projectOpen the project in Claude Code and run:
initialize
This resets the template for your project and asks what you want to build.
The agents take over from here. They'll ask questions when needed and keep you informed of progress.
To resume work in a new session:
continue
| Command | When to Use |
|---|---|
initialize |
Once, right after cloning the template |
continue |
To resume work in a new Claude Code session |
| Agent | What It Does |
|---|---|
| Requirements | Interviews you to understand what you want to build |
| Architect | Makes technology choices, defines project structure |
| Designer | Creates detailed designs with UML diagrams |
| Task Manager | Coordinates all agents, tracks progress |
| Test Designer | Plans what tests are needed |
| Data Agent | Defines database schemas and data structures |
| Deployment | Sets up Docker, environment configs, infrastructure |
| Developer | Writes application code |
| Test Coder | Writes test code |
| Test Runner | Runs tests, diagnoses failures |
| Test Debugger | Deep debugging across all layers when tests fail |
| Code Reviewer - Requirements | Verifies code completeness against requirements |
| Code Reviewer - Security | Checks for OWASP vulnerabilities |
| Code Reviewer - Integration | Finds stubs, incomplete code, wiring gaps |
| Documentation | Writes user guides and developer docs |
Pre-built coding and testing conventions for 27 technologies:
Backend Languages
- Go, Java, Python, TypeScript, Rust, C#/.NET, Ruby, PHP, Kotlin, Scala, Elixir
Frontend Frameworks
- React, Vue, Angular, Svelte, Next.js, Nuxt
Mobile
- Swift, Kotlin Android, Flutter/Dart, React Native
Infrastructure & DevOps
- Terraform, Kubernetes, Bash/Shell, SQL
Emerging & Specialized
- Zig, Solidity
The Developer and Test Coder agents automatically use the right conventions for your tech stack.
After initialization, your project will have:
your-project/
├── .claude/agents/ # Agent definitions (don't modify)
├── Claude.md # Project memory and status
├── conventions/ # Coding standards by language
├── project-docs/ # Requirements, designs, task lists
│ ├── adrs/ # Architecture decisions
│ └── schemas/ # Data schemas
├── developer-docs/ # Docs for contributors
└── user-docs/ # Docs for end users
- Document-based coordination - Agents communicate through markdown files, not complex APIs
- Task Manager as orchestrator - One agent controls the workflow and task list
- Schemas as source of truth - Data Agent maintains schemas that all code references
- Smart failure routing - When tests fail, the system figures out which agent should fix it
- Be specific in requirements - The more detail you provide upfront, the better the output
- Answer agent questions thoughtfully - They ask for a reason
- Review designs before implementation - Easier to change a design than refactor code
- Use
continueliberally - Sessions can be interrupted; progress is saved
- cursor-startup - Similar template for Cursor IDE
MIT