gsd-cc-plan

Generate executable task plans with BDD acceptance criteria and boundaries.

3|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cc-plan
Source: https://github.com/0ui-labs/GSD-CC/tree/main/gsd-cc/skills/plan
Command: npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans a slice description into a set of executable task plans with explicit boundaries and BDD-style acceptance criteria, enabling deterministic execution and easier verification.

Core Features & Use Cases

  • Generates task-level plans from slice descriptions with clearly defined acceptance criteria and boundaries.
  • Produces inputs for subsequent steps like /gsd-cc-apply or auto-loop.sh, ensuring a smooth handoff between planning and execution.
  • Aligns planning with project state and CLAUDE templates to preserve context and traceability.

Quick Start

Describe a target slice to produce a ready-to-run plan for execution.

Frequently Asked Questions about gsd-cc-plan

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

FAQPage Schema
How do I generate executable task plans with BDD acceptance criteria?

To generate task plans with BDD acceptance criteria, you provide a slice description to produce structured, executable tasks. This enforces explicit boundaries and state-aware planning for deterministic execution and easier verification.

What is the best way to decompose a software slice for automated execution?

Decomposing a software slice for automated execution involves structuring the description into traceable task plans. This process aligns with project state and CLAUDE templates to preserve context and feed subsequent execution loops.

Can I use CLAUDE templates for state-aware task planning?

Yes, state-aware task planning integrates directly with existing CLAUDE templates. This alignment preserves project context and ensures traceable outputs when converting slice descriptions into actionable workflows.

How do I feed a structured task plan into an automated execution loop?

You feed a structured task plan into an automated execution loop by routing the slice to produce ready-to-run inputs. These generated plans serve as direct inputs for subsequent execution steps like auto-loop.sh.

Does state-machine based workflow planning require explicit task boundaries?

State-machine based workflow planning requires explicit boundaries to ensure deterministic execution. Defining these boundaries alongside BDD-style acceptance criteria prevents scope creep and enables easier verification of each task.