create-meta-prompts
Create optimized prompts for Claude-to-Claude pipelines with research, planning, and execution stages. Use when building prompts that produce outputs for other prompts to consume, or when running multi-stage workflows (research -> plan -> implement).
npx skills add majiayu000/claude-skill-registry --skill create-meta-prompts-devattom-claude --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Creates prompts optimized for Claude-to-Claude pipelines across research, plan, and implement stages. Each prompt produces outputs suitable for consumption by subsequent prompts and stores artifacts in a structured folder under .prompts/ with a SUMMARY.md for quick human scanning.
How it works
- Intake and chain detection determine purpose and topic, then generate a prompt using purpose-specific patterns.
- Saves prompts to a new folder in .prompts/{number}-{topic}-{purpose}/ with a completed/ subfolder once run.
- Each generated prompt includes sections: Objective, Context, Requirements, Output specification, Metadata requirements (for research/plan), SUMMARY.md requirement, and Success criteria.
- For Research/Plan prompts, outputs include <confidence>, <dependencies>, <open_questions>, and <assumptions> in XML metadata.
- SUMMARY.md is created describing one-liner, Version, Key Findings, Files Created (for Do prompts), Decisions Needed, Blockers, and Next Step.
- Execution uses a dependence-aware engine to run prompts in order, with artifact archiving and progress reporting.
When to use it
Use to build prompts that feed other prompts or run multi-stage workflows (research -> plan -> implement). The system detects existing research or plan files to reference and guides the user through a decision tree before creation.
What it can touch
- Creates folders and files under .prompts/ and its subfolders.
- Writes prompts to .prompts/{number}-{topic}-{purpose}.md and outputs to .prompts/{number}-{topic}-{purpose}/{topic}-{purpose}.md.
- Archives completed prompts into .prompts/{number}-{topic}-{purpose}/completed/.
Caveats
- License: MIT
- If dependencies are missing or references do not exist, it may prompt to create missing prompts first or offer recovery options as described in the workflow. All actions are described in the generation and execution steps without guaranteeing outcomes.
<objective> Create prompts optimized for Claude-to-Claude communication in multi-stage workflows. Outputs are structured with XML and metadata for efficient parsing by subsequent prompts. Every execution produces a `SUMMARY.md` for quick human scanning without reading full outputs. Each prompt gets its own folder in `.prompts/` with its output artifacts, enabling clear provenance and chain detection. </objective> <quick_start> <workflow> 1. **Intake**: Determine purpose (Do/Plan/Research/Refine), gather requirements 2. **Chain detection**: Check for existing research/plan files to reference 3. **Generate**: Create prompt using purpose-specific patterns 4. **Save**: Create folder in `.prompts/{number}-{topic}-{purpose}/` 5. **Present**: Show decision tree for running 6. **Execute**: Run prompt(s) with dependency-aware execution engine 7. **Summarize**: Create SUMMARY.md for human scanning </workflow> <folder_structure> ``` .prompts/ ├── 001-auth-research/ │ ├── completed/ │ │ └── 001-auth-research.md # Prompt (archived after run) │ ├── auth-research.md # Full output (XML for Claude) │ └── SUMMARY.md # Executive summary (markdown for human) ├── 002-auth-plan/ │ ├── completed/ │ │ └──
mv .prompts/{number}-{topic}-{purpose}/{number}-{topic}-{purpose}.md \What does the create-meta-prompts skill do?
Create optimized prompts for Claude-to-Claude pipelines with research, planning, and execution stages. Use when building prompts that produce outputs for other prompts to consume, or when running multi-stage workflows (research -> plan -> implement).
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill create-meta-prompts-devattom-claude --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.