prompt-generator

Generates phase-based orchestration prompts from templates and saves them to docs/prompts.

17|1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/mhylle/claude-skills-collection --skill prompt-generator-mhylle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-generator
Source: https://github.com/mhylle/claude-skills-collection/tree/main/skills/prompt-generator
Command: npx skills add https://github.com/mhylle/claude-skills-collection --skill prompt-generator-mhylle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill reduces the manual overhead of designing consistent orchestration prompts for phase-based project implementations, enabling teams to quickly generate repeatable instructions for subagents and maintainable prompts for future phases.

Core Features & Use Cases

  • Structured prompt templates for each project phase and integration with phase plans
  • Automatic saving to docs/prompts using the save_prompt.py tool
  • Consistent naming convention: phase-<N>-<name>.md for auto-discovery
  • Supports ADR integration and general-plan guidance for onboarding new phases
  • Ideal for teams practicing orchestration-based execution and multi-agent coordination

Quick Start

Trigger the skill to generate prompts for a given phase, supply phase number, phase name, phase doc path, and project root. The produced prompt is saved to docs/prompts and can be used by implement-plan/implement-phase workflows.

Frequently Asked Questions about prompt-generator

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

FAQPage Schema
How do I generate structured orchestration prompts for phase-based project implementation?

To generate orchestration prompts for phase-based project implementation, trigger the skill with the phase number, phase name, phase doc path, and project root. It reads templates and phase plans, substitutes placeholders, and saves the generated prompt to the docs/prompts directory.

What is the naming convention for saving generated prompts for subagent delegation?

The naming convention for saving generated prompts for subagent delegation is phase-<N>-<name>.md. This structured format ensures auto-discovery and consistent organization within the docs/prompts directory for future phase-based implementations.

How do I integrate ADR and general-plan guidance into generated prompt templates?

You can integrate ADR and general-plan guidance into generated prompt templates by supplying the respective phase doc path and project root. The skill reads these documents to substitute placeholders and incorporate onboarding guidance for new project phases.

Does this prompt generation approach work with multi-agent coordination workflows?

Yes, this prompt generation approach works with multi-agent coordination workflows. It is specifically designed for teams practicing orchestration-based execution, automatically producing repeatable instructions for subagent delegation across multiple implementation phases.

What inputs do I need to provide to trigger the prompt generation for a new project phase?

To trigger prompt generation for a new project phase, you need to provide the phase number, phase name, phase doc path, and project root. The tool uses these inputs to read the necessary templates and save the final output using the save_prompt.py script.

When do I need structured prompt templates for phase-based planning?

You need structured prompt templates for phase-based planning when managing multi-step implementations that require subagent delegation. This approach reduces manual overhead by maintaining consistent, repeatable instructions for orchestration-based execution across project phases.