planning

Plan research into phase workflows with validation gates and approvals.

Updated Apr 4, 2026

Search Tags:#planning #context #validation #beads #governance #phase-plan #swarming

Ready to run

npx skills add https://github.com/anionzo/skill --skill planning-anionzo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/anionzo/skill/tree/main/skills/planning
Command: npx skills add https://github.com/anionzo/skill --skill planning-anionzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans research into actionable phase workflows and gating criteria to reduce execution risk.

Core Features & Use Cases

Transform CONTEXT.md and discovery results into a Phase Plan and Phase Contract.
Generate a Phase Story Map and Bead graph, coordinating dependencies and approvals for safe swarming.
Enforce the Validation Gate before execution and track State transitions in .anionzo/STATE.md.

Quick Start

Lock the CONTEXT, run discovery and synthesis, approve the phase plan, and prepare the current-phase artifacts for execution.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I turn research context into an actionable phase plan for feature development?▼

You turn research context into an actionable phase plan by transforming CONTEXT.md and discovery results into phase workflows with gating criteria. This organizes features, phase plans, and stories to reduce execution risk before development begins.

What is a validation gate in phase planning and when do I need it?▼

A validation gate is an enforced entry and exit state requiring explicit approvals before any code is written. You need it to reduce execution risk, ensure safe handoffs to swarming, and track state transitions in STATE.md.

How do I coordinate dependencies and approvals for swarming during feature planning?▼

You coordinate dependencies and approvals for swarming by generating a phase story map and bead graph. These artifacts map dependencies and required explicit approvals, ensuring safe handoffs and organized execution for swarming teams.

Does this phase planning approach work without writing code first?▼

Yes, this phase planning approach works without writing code first by enforcing validation gates and explicit approvals before development starts. It organizes work into beads and stories, reducing execution risk prior to swarming.

What's the best way to manage state transitions across multiple phase plans?▼

The best way to manage state transitions across phase plans is to track them explicitly in STATE.md. This enforces entry and exit states, validation gates, and explicit approvals, ensuring clear handoffs and safe swarming execution.