Menu
Start a new plan-writing session. Explores the codebase and asks clarifying questions.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/imbue-ai/default-workspace-template --skill blueprintThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Based on SOC occupation classification
| name | blueprint |
| description | Start a new plan-writing session. Explores the codebase and asks clarifying questions. |
| metadata | {"author":"imbue"} |
Start a new plan-writing session. Help the user write an implementation plan through multi-round Q&A.
Parse the user's message for the feature description.
Read references/templates.json to get the available templates. Ask the user which template they'd like to use — one per template, using the template's name as the label and description as the description. Always include an "Other" option so the user can describe a custom template.
This is the ONLY time you should ask a template selection question during the session.
Read the selected template's prompt field to understand the structure and level of detail expected. If the user selected "Other", use their custom description as the template prompt.
Your questions should match the template's level and perspective.
Explore the project to understand:
Spend real effort here. Read actual source files.
Help the user think through everything they'd need to answer in order to write that plan well.
Based on the codebase exploration, ask 3-5 clarifying questions following the format in .
Guidelines:
Before the questions, add this hint:
> Answer with shorthand like `1a, 2b, 3e, 4a, 5b` or write freely.
After the questions, add:
Once you're done answering, I'll follow up with more questions. When you're ready, invoke the blueprint-generate skill to end the Q&A and generate the plan.
Wait for the user to respond. Accept answers in any format:
1a, 2b, 3e or 1a 2b 3e1a, 2b, 3. I think we should...When they answer:
* syntax) incorporating all clarifications so far. Follow the rules in references/refine-prompt.md. Display it in a blockquote so the user can see how their answers are shaping the plan.IMPORTANT: Do NOT stop asking questions on your own. Only the user decides when Q&A is done by invoking blueprint-generate. Do NOT generate the plan. Do NOT write or modify any code files — you are only gathering information.
Once a feature description has been provided and a template selected, append a single progress line at the end of every message. Do NOT show the progress line before then (e.g. when asking for a missing feature description or during template selection).
The line shows all four workflow phases using ✓ (completed), ● (active), ○ (pending). Explore completes before the first user-visible question, so always show:
✓ Explore ● Plan ○ Write ○ Refine
Place the line after all other content, separated by a blank line.