deep-project plugin
A Claude Code plugin that turns vague requirements into numbered spec files with a dependency manifest through an interview.
- 222 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- A hook runs a Python script through `uv run` at every session start.
- The plugin creates directories and spec files next to the requirements file.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/deep-projectDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A hook runs a Python script through `uv run` at every session start.
- The plugin creates directories and spec files next to the requirements file.
This is third-party code. Review the repository files before installing.
What it does
deep-project takes a file of vague requirements, such as `planning/requirements.md`, and splits the project into parts that can each be planned separately. The `/deep-project @planning/requirements.md` command walks through seven steps: input validation, an adaptive interview, split analysis, dependency mapping, your confirmation of the structure, creation of numbered directories and a `spec.md` for each part. The planning directory ends up with the interview transcript `deep_project_interview.md`, the manifest `project-manifest.md` with a dependency graph, a recommended execution order and a machine-readable `SPLIT_MANIFEST` block, plus `splits/01-…/spec.md` folders. An interrupted run resumes from the right step when you launch it again with the same file. The specs are meant for `/deep-plan`, the next plugin in the same series.
Who it is for. Founders and tech leads who start a large project with a brief like "build a SaaS platform" and are unsure how to cut it into subsystems.
Good fit when
- Requirements are vague: a platform with authentication, billing and two dashboards is wanted.
- The project has several subsystems and you want to plan them in parallel sessions.
- Dependencies between modules are unclear and the implementation order should be pinned down in a manifest.
- The interview broke off on a context limit and the work continues from the same step.
- `/deep-plan` expects specs as input and every part should be planned separately.
Not a fit when
- The task is one clear feature, a bug fix or a small tweak: the plugin would still frame it as a single part.
- Requirements are already split into finished specs and the interview would add nothing.
- Python 3.11 and the uv package manager are missing: the plugin depends on them.
- You need a ready implementation plan with code: the plugin stops at specs and `/deep-plan` builds the plan.
Example request
/deep-project @planning/requirements.mdLimitations
Version 0.2.1 is marked beta. You need Claude Code, Python 3.11 or newer and the uv package manager, and no external API keys are required, unlike `/deep-plan`. The plugin only produces specs and a manifest: the implementation plan and code come from `/deep-plan` and `/deep-implement`, which install separately. A `SessionStart` hook runs a Python script through `uv run` to remember the session id. The quality of the split depends on your interview answers, and the manifest is worth reading before the specs are generated. The last commit is dated June 2026.
How to disable. Disable the plugin through `/plugins` or remove it with `/plugin uninstall deep-project`. The `planning/` directory with results stays on disk.
FAQ
How do I install deep-project in Claude Code?
Run `/plugin marketplace add piercelamb/deep-project`, then `/plugin install deep-project` and `/plugin enable deep-project`. You need `uv` and Python 3.11 or newer.
What if the run gets interrupted?
Launch the same command with the same requirements file. The plugin finds the finished artifacts and resumes from the right step; on a state conflict it asks whether to resume or start fresh.
How does deep-project differ from deep-plan?
deep-project splits a vague project into parts and writes specs. `/deep-plan` takes one spec and builds a plan from it with research, external model review and a TDD approach.
How long does the interview take?
The author estimates about 15 minutes of questions and answers. Requirements can be vague, and the interview draws out the details.
Are API keys required?
No. Dependencies are managed by `pyproject.toml`, and no external keys are needed, unlike `/deep-plan`.
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 for large specs: requirements with proof obligations, a walking skeleton and audited sprints
A Claude Code plugin: spec-driven development over a single SPEC.md file, a loop of seven commands with no sub-agents
A Claude Code plugin that interviews you, designs the architecture and writes a self-contained blueprint to build from
A marketplace of 23 plugins for Claude Code: git and pull requests, code review, TDD, specs and delegation to other models
A skill that interviews you and writes requirements.md, design.md and tasks.md so Claude Code and Cursor work from one plan
README in short
The plugin opens a series of three: `/deep-project` splits, `/deep-plan` plans, `/deep-implement` writes code. The author, Pierce Lamb, covered the series and its technical lessons in two Medium articles.