Agent skill
ralph-planning-artifact-templates
Ralph-v2 planning artifact templates and task decomposition scaffolding. Use when creating or updating `plan.md`, `progress.md`, `metadata.yaml`, iteration metadata, or isolated task files during INITIALIZE, UPDATE, TASK_BREAKDOWN, REBREAKDOWN, or SPLIT_TASK.
Install this agent skill to your Project
npx add-skill https://github.com/arisng/github-copilot-fc/tree/main/skills/ralph-planning-artifact-templates
SKILL.md
Ralph Planning Artifact Templates
This skill centralizes the canonical Ralph-v2 planning artifacts so the Planner prompt can stay focused on judgment and decomposition.
Core Artifacts
metadata.yamliterations/<N>/metadata.yamliterations/<N>/plan.mditerations/<N>/progress.mditerations/<N>/tasks/task-<id>.md
Session Metadata Template
version: 1
session_id: <SESSION_ID>
created_at: <ISO8601>
updated_at: <ISO8601>
iteration: 1
orchestrator:
state: PLANNING
current_wave: null
tasks:
total: 0
completed: 0
failed: 0
pending: 0
session_review:
cycle: 0
issue_severity_threshold: "any"
max_critique_cycles: null
Iteration Metadata Template
version: 1
iteration: <N>
started_at: <ISO8601>
planning_complete: false
planning_completed_at: null
completed_at: null
tasks_defined: 0
Plan Template
# Plan - Iteration <N>
## Goal
[Concise goal]
## Success Criteria
- [ ] SC-1: [Measurable criterion]
## Target Files
| File | Role | Changes Expected |
|------|------|------------------|
## Context
[Background and constraints]
## Approach
[Strategy and key decisions]
## Waves
| Wave | Tasks | Rationale |
|------|-------|-----------|
## Grounding
[Q-IDs and Issue-IDs that justify the plan]
Progress Template
# Progress
## Legend
- `[ ]` Not started
- `[/]` In progress
- `[P]` Pending review
- `[x]` Completed
- `[F]` Failed
- `[C]` Cancelled
## Planning Progress (Iteration <N>)
- [ ] plan-init
- [ ] plan-brainstorm
- [ ] plan-research
- [ ] plan-breakdown
## Implementation Progress (Iteration <N>)
[To be filled]
Task File Template
---
id: task-1
iteration: <N>
wave: 1
type: Sequential
created_at: <ISO8601>
updated_at: <ISO8601>
---
# Task: task-1
## Title
[Short title]
## Files
- path/to/file
## Objective
[What this task achieves]
## Grounded In
- Q-000
- ISS-000
## Success Criteria
- [ ] [Measurable criterion]
## Dependencies
depends_on: []
inherited_by: []
Decomposition Rules
- Every task needs at least 2 grounding references, including at least 1 Q-ID.
waveis required for Orchestrator batch routing.- Prefer parallel waves; add dependencies only when correctness requires them.
- Split oversized tasks into 2-4 narrower tasks while preserving dependency semantics.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
fleet
Multi-iteration parallel subagent orchestrator for Kimi Code CLI with streamlined observability, automated documentation, and atomic commits. Use when orchestrating complex work across multiple subagents, enabling parallel execution, or when explicitly requesting fleet mode with '/flow:fleet'. Integrates diataxis documentation and git-atomic-commit workflow.
github-pages-deploy
Deploy a static HTML file or static site directory to GitHub Pages. Use when the user wants a durable GitHub-hosted URL for a static page, diagram, report, or generated site, and can provide GitHub authentication via GITHUB_TOKEN or GH_TOKEN.
Didn't find tool you were looking for?