blueprint-generate
Skill527 starsChanged 4 months agoMITView on GitHub
End the Q&A phase and generate the plan. Use after the blueprint skill has gathered enough context.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- tymrtn/tomorrowkit-for-mindsedited, first seen Aug 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- tymrtn/tomorrowkit-for-minds★ 491% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- blueprintSkill
- domain-settingsSkill
- leaflet-ai-apiSkill
- lexiconsSkill
- mirror-editor-block-stylesSkill
- notificationsSkill
- publication-settingsSkill
- specSkill
- tests-postsSkill
- tests-subscribeSkill
- update-default-themeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Create a concise 2-5 word kebab-case slug (max 50 chars) for the feature.
- Distinctive: line 26
Use the most recent refined prompt from the Q&A conversation.
- Distinctive: line 38
Place the line after all other content, separated by a blank line.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blueprint — Generate plan
Generate an implementation plan from the Q&A session.
Step 1: Resolve template
Recall the template name from the blueprint Q&A conversation. Read references/templates.json and find the matching template.
Step 2: Generate slug
Create a concise 2-5 word kebab-case slug (max 50 chars) for the feature. Sanitize: lowercase, alphanumeric + hyphens only, no leading/trailing hyphens. If blueprint/<slug> already exists, append -2, -3, etc.
Step 3: Create plan directory
mkdir -p blueprint/<slug>Step 4: Refine the prompt
Use the most recent refined prompt from the Q&A conversation. If for any reason it wasn't shown during Q&A, generate it now — see references/refine-prompt.md.
Step 5: Write the plan
See references/write-plan.md.
Append this progress line at the end of every message during the Write phase:
✓ Explore ✓ Plan ● Write ○ RefinePlace the line after all other content, separated by a blank line.
Step 6: Refinement
See references/refinement.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.