skills.rest
tuvens
tuvensCOMMUNITY
Explore all skills by this author →
GitHub

writing-phase-prompts

Create an ORCHESTRATION-PROMPT.md for multi-phase software projects.

Updated Aug 27, 2026
Search Tags:#claude code#orchestration#phase planning#sprint 0#prompt authoring#branch conventions
One-click install
npx skills add https://github.com/tuvens/phased-development --skill writing-phase-prompts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-phase-prompts
Source: https://github.com/tuvens/phased-development/tree/main/skills/writing-phase-prompts
Command: npx skills add https://github.com/tuvens/phased-development --skill writing-phase-prompts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps a VP of Engineering or orchestrator create a high-quality ORCHESTRATION-PROMPT.md when a new phase needs to be planned by hand, migrated from an existing project, or documented as a special case.

Core Features & Use Cases

It turns phase-planning requirements into a complete prompt that covers role definition, sprint sequencing, quality expectations, merge gates, naming conventions, and complexity guidance. It is especially useful when a project is moving through a new phase, when the latest conventions must be preserved from recent phases, or when the standard /start-phase flow is not the right fit. It also ensures the generated prompt references the testing and codex delegation conventions required by the broader phased-development workflow.

Quick Start

Use this skill to draft an ORCHESTRATION-PROMPT.md for the next phase of our project, following the repository template and the latest phase conventions.

Frequently Asked Questions about writing-phase-prompts

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

FAQPage Schema
How do I draft an orchestration prompt for multi-phase software projects?▼

Drafting an orchestration prompt involves defining role expectations, sprint sequencing, merge gates, and naming conventions into a structured ORCHESTRATION-PROMPT.md file. This ensures the multi-phase software project follows standardized quality directives and testing protocols.

What is Sprint 0 in phase orchestration planning?▼

Sprint 0 in phase orchestration planning is the initial setup sequence required within an ORCHESTRATION-PROMPT.md. It establishes branch conventions, complexity ratings, and codex delegation references before active development sprints begin.

When should I hand-author a phase orchestration prompt instead of using standard flows?▼

Hand-authoring a phase orchestration prompt is necessary when migrating existing phases, documenting special cases, or preserving the latest conventions for mature projects where the standard automated flow does not fit.

How do I document merge order and naming conventions for a new project phase?▼

Documenting merge order and naming conventions requires specifying branch rules and integration sequences within the ORCHESTRATION-PROMPT.md. This defines how code branches merge sequentially to maintain stability across the phase.

Does phase orchestration require codex delegation references?▼

Phase orchestration requires codex delegation references to connect the prompt with broader testing protocols and delegation conventions. This ensures the generated ORCHESTRATION-PROMPT.md aligns with the required phased-development workflow.

What limitations exist when migrating existing phases to a new orchestration plan?▼

Migrating existing phases to a new orchestration plan requires manually mapping prior conventions to the required phase-prompt structure. Limitations arise if the source project lacks clear documentation for merge order, complexity ratings, or testing protocols.

Related Skills

Explore More Software Engineering Skills→
danghungtb26danghungtb26
3

project-conventions

Enforce naming and folder structure conventions for React TypeScript admin templates.

Community
Basic
mayurpisemayurpise
39

status

Summarize Draft track progress, phases, completion, and blockers from project files.

Community
Intermediate
nnexainnexai
1

gsd-ship

Automate branch pushing, pull request creation, and merge tracking for git workflows.

Community
Advanced
StudentCristianStudentCristian

nw-pbt-erlang-elixir

Automate property-based testing for Erlang/Elixir projects with PropEr, PropCheck, and StreamData.

Community
Intermediate