The Agentic Startup plugin
Claude Code plugins for spec-driven development: specify, implement and review commands plus specialist agents
- 575 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The install script runs through curl and sh and edits Claude Code settings, so read it beforehand
- The implementation and refactoring commands change project files and run tests, and some flows reach branches, commits and pull requests
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/the-agentic-startupDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The install script runs through curl and sh and edits Claude Code settings, so read it beforehand
- The implementation and refactoring commands change project files and run tests, and some flows reach branches, commits and pull requests
This is third-party code. Review the repository files before installing.
What it does
The Agentic Startup is a set of plugins that moves Claude Code to spec-driven development. The `/specify` command first creates the requirements and the technical solution, and only then do agents write code. A classifier rates the complexity and proposes one of three tiers: direct, incremental with a phased plan, or factory with parallel work on independent units. The main `start` plugin holds ten commands grouped into setup, build and maintain phases. The core of the cycle is `/specify`, `/validate` and `/implement`. The `/review` command examines changes with several agents from different angles, and `/test` fixes failing tests even if the failure predates your changes. On hard bugs `/debug` sets several hypotheses against each other. The optional `team` plugin adds specialist agents, from an analyst and an architect to a platform engineer, plus a chief coordinator. Specifications are stored in the `.start/specs` folder, and the `/constitution` command records project-wide rules.
Who it is for. For developers in Claude Code who want requirements and the technical design as files in the project.
Good fit when
- A new feature touches several components and you want a requirements and design document before any code
- You want to check a specification for completeness and contradictions before implementation with the `/validate` command
- You want implementation to follow a ready Markdown plan with deviations from the spec caught automatically
- You need a review of changes from several angles: concurrency, dependencies, interface accessibility
Not a fit when
- A one-line edit or a quick fix: the specification cycle takes 15 to 30 minutes and is overkill for small things
- You use a different agent: the plugins work only in Claude Code
- Your team already uses another spec-driven system and does not want to combine two
Example request
`/specify Add real-time notification system with WebSocket support`Limitations
You need Claude Code 2.0 or newer with marketplace support. Large specifications and implementations hit the context window. Then you continue in a new session with the same command and the spec number, for example `/implement 001`: progress is kept in the spec files. The Agent Teams mode is still experimental. The install script also changes the output style and adds a status line, and after removing the plugins you revert those by hand. The last commit was made in August 2026.
How to disable. Remove the plugins with `/plugin uninstall start@the-startup` and `/plugin uninstall team@the-startup`, and drop the marketplace from the list. Revert the status line and output style the script installed through the Claude Code settings. The status line config lives in `~/.config/the-agentic-startup/statusline.toml`. The `.start/specs` folder stays in your projects as ordinary Markdown files.
FAQ
How do I install The Agentic Startup in Claude Code?
By hand: run `/plugin marketplace add rsmdt/the-startup`, then `/plugin install start@the-startup`, and optionally `/plugin install team@the-startup`. The quick route: run the install script with `curl -fsSL https://raw.githubusercontent.com/rsmdt/the-startup/main/install.sh | sh`.
What are the three specification complexity tiers?
The direct tier suits fixes and small features and creates no plan. The incremental tier gives a phased TDD plan for one feature with one or two components. The factory tier describes units and scenarios for several features and runs independent units in parallel. `/specify` picks the tier, and you can change it.
Can I implement a plan written without `/specify`?
Yes. The `/implement` command accepts any Markdown plan, for example `/implement path/to/plan.md`, including architecture documents and migration guides.
How do the Startup and ScaleUp output styles differ?
The Startup writes with energy and sets the pace. It suits fast sprints. The ScaleUp is calm and briefly explains decisions as it works, so it is useful when getting to know someone else's codebase. You switch the style with `/output-style`.
How do I enable the Agent Teams mode?
The installer offers to set it up. By hand, add an env block with the `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` variable set to `1` to `~/.claude/settings.json`. In this mode the specialists coordinate among themselves.
Discussion
No questions or reviews yet.
Related
PluginsA plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A Claude Code plugin: spec-driven development over a single SPEC.md file, a loop of seven commands with no sub-agents
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
A plugin with ready, go and migration commands: it settles what you want first, then builds and verifies the result
A plugin for Claude Code and Codex: turns a feature request into a spec and executes it task by task with fresh context
Two skills for spec-driven development: /spec asks questions and saves a document to specs/, /spec-impl implements an approved spec step by step
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| The Agentic Startup (this entry) | no | 575 | |
| Spec Kit | no | 143,920 | GitHub's toolkit with a specify CLI that adds commands and skills for various agents to a project |
| OpenSpec | no | 73,368 | spec-driven development for coding agents: proposal, requirements, design and tasks before code |
| Pilot Shell | no | 2,106 | a ready harness for Claude Code and Codex with TDD, memory between sessions and quality gates |
README in short
The project page opens with a diagram of the ten commands and a tree for picking the right one. It continues with a step-by-step look at the specification cycle, tables of plugins and agents, and a section on the status line with color thresholds.