create-meta-prompts

Create reusable metadata-rich prompts for Claude-to-Claude workflows.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill create-meta-prompts-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-meta-prompts
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/create-meta-prompts
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill create-meta-prompts-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill centralizes the creation of multi-step prompts that produce structured outputs for Claude-to-Claude pipelines. It ensures consistent frontmatter, naming conventions, and a traceable provenance trail across chained prompts.

Core Features & Use Cases

  • Patterned prompt generation: builds Do/Plan/Research prompts from reusable templates.
  • Structured outputs: emits outputs with XML metadata suitable for downstream parsing.
  • Provenance & chaining: automatically references existing research/plans and stores artifacts under a standardized .prompts structure.
  • Extensibility: supports optional resources (scripts/references/assets) for extended workflows.

Quick Start

Use the /create-meta-prompt command to start a new prompt chain. Example: /create-meta-prompt research authentication options for the app The command will identify purpose and topic, reference any existing research/plans, and produce a new prompt folder at .prompts/ with a structured file ready for execution.

Frequently Asked Questions about create-meta-prompts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create multi-stage prompts for Claude-to-Claude workflows?

Multi-stage prompts for Claude-to-Claude workflows are created by generating structured files with standardized frontmatter, explicit dependencies, and XML metadata to ensure deterministic downstream composition.

What is provenance and why does it matter for chained prompt engineering?

Provenance in chained prompt engineering provides a traceable trail across research, plan, and implement stages. It automatically references existing artifacts so downstream prompts execute deterministically without losing context.

How do I structure prompt artifacts for deterministic downstream parsing?

Prompt artifacts are structured under a standardized .prompts folder using enforced frontmatter and XML metadata outputs. This organization allows downstream prompts to parse and compose execution sequences deterministically.

Can I add external scripts and references to a multi-stage prompt chain?

Yes, multi-stage prompt chains support optional resources including scripts, references, and assets. These extensible resources are integrated into the workflow to support extended prompt execution sequences.

What's the best way to organize research and planning prompts for automation?

Organizing research and planning prompts for automation requires centralizing them under a standardized folder structure with consistent naming conventions. This ensures structured outputs and traceable provenance across chained prompts.