Help us improve
Share bugs, ideas, or general feedback.
From optimus
Scaffolds empty, product-neutral docs-first spec cascade (product vision, MVP PRD, tech stack) for a human to fill before writing code. Safe to run on any project; never overwrites existing docs.
npx claudepluginhub oprogramadorreal/optimus-claude --plugin optimusHow this skill is triggered — by the user, by Claude, or both
Slash command
/optimus:spec-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are scaffolding a **docs-first cascade**: a small set of empty, human-fillable steering documents that capture product direction *before* any code exists. This is optimus's bootstrap for spec-driven development.
Writes structured specifications before coding. Use when requirements are ambiguous, starting a new project/feature, or changes touch multiple files.
Creates production-grade PRD for greenfield projects via discovery interview, battle-tested architecture defaults, adversarial analysis, and sprint-ready specs output.
Share bugs, ideas, or general feedback.
You are scaffolding a docs-first cascade: a small set of empty, human-fillable steering documents that capture product direction before any code exists. This is optimus's bootstrap for spec-driven development.
What you produce (three skeletons under the project root, all product- and tool-neutral):
docs/product/product-context.md — the long-term product vision.docs/product/mvp-prd.md — the first product slice (MVP PRD).docs/product/tech-stack.md — the target technology stack.The boundary — do not cross it. You emit empty skeletons with TODO markers for a human to fill. You author no product content — no personas, no metrics/KPIs, no business-value prose, no technology choices. optimus is an engineering tool; the cascade is product/PM territory that a human owns. The engineering build spec is authored later by /optimus:brainstorm (in docs/specs/), not here. See $CLAUDE_PLUGIN_ROOT/references/sdd-mapping.md for the full contract.
$CLAUDE_PLUGIN_ROOT/skills/init/references/multi-repo-detection.md and scaffold at the appropriate level (workspace root vs. a subproject) rather than blindly in the current folder.For each of the three target files, check whether it already exists:
exists → skipped.If all three already exist, the cascade is already scaffolded: report that and skip to Step 4.
$CLAUDE_PLUGIN_ROOT/skills/spec-init/references/cascade-templates.md.docs/product/) and write the matching template block verbatim to its target path. Do not fill in the TODO markers — that is the human's job.docs/specs/ — the buildable spec is authored later by /optimus:brainstorm or dropped in by a human, in docs/specs/; see the contract;.claude/ (settings, hooks, .optimus-version, or docs) — agent/project setup is /optimus:init's job, not this skill's;Summarize what was created vs. skipped.
Tell the user to fill the TODO sections top-down (vision → MVP PRD → target stack), and state the precedence (the canonical rule lives in $CLAUDE_PLUGIN_ROOT/references/sdd-mapping.md and is restated in each scaffolded doc's header) so they know how the docs relate: higher docs set long-term direction; the active build spec governs what to build right now — when they conflict about current work, the active build spec wins.
Close with the handoff tip. This is not a continuation skill (the human fills the docs out-of-band and /optimus:brainstorm gathers its own context), so use the default — Variant C in $CLAUDE_PLUGIN_ROOT/references/skill-handoff.md:
Next step: fill in the cascade's
TODOsections (vision → MVP PRD → target stack). Then run/optimus:brainstormto design the first build — it reads the cascade as steering and writes the engineering spec todocs/specs/.Tip: for best results, start a fresh conversation for the next skill — each skill gathers its own context from scratch.