ce:plan

Translate feature descriptions into structured implementation plans with test scenarios.

6|Updated Jan 29, 2023
One-click install
npx skills add https://github.com/rethinkhealth/glion --skill ce-plan-rethinkhealth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:plan
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/ce-plan
Command: npx skills add https://github.com/rethinkhealth/glion --skill ce-plan-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate vague or defined requirements into structured, execution-ready plans that teams can implement.

Core Features & Use Cases

  • Generate a complete set of implementation units with goals, dependencies, and test scenarios from a user-provided description or requirements document.
  • Anchor planning to repository patterns and research notes to ensure consistency and traceability.
  • Produce a plan file and metadata, enabling handoff to development and QA.

Quick Start

Provide a feature description or requirements, and ce:plan will generate a structured, implementation-ready plan with defined units.

Frequently Asked Questions about ce:plan

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

FAQPage Schema
How do I turn software requirements into an actionable development plan?

Turn software requirements into an actionable development plan by translating feature descriptions into discrete implementation units with defined goals, dependencies, files, and test scenarios. This generates a structured plan file and metadata for direct handoff to development and QA.

What is the best way to ensure traceability from requirements to test scenarios?

To ensure traceability from requirements to test scenarios, anchor your planning to repository patterns and research notes. Generating per-unit fields with explicit test scenarios maintains clear linkage from initial requirements through implementation.

Can I generate implementation units from a vague product requirements document?

Yes, you can generate implementation units from a vague product requirements document. The planning process translates undefined or defined requirements into structured, execution-ready units complete with goals, required files, and dependency mapping.

Does structured project planning work for research-driven initiatives?

Structured project planning works for research-driven initiatives by converting research notes and descriptions into discrete implementation units. It outputs a plan file path with per-unit fields, ensuring research outcomes are actionable and traceable.

How do I start creating an execution-ready plan for a new software feature?

To start creating an execution-ready plan for a new software feature, provide a feature description or requirements document. The system outputs a structured plan with defined implementation units, dependencies, and test scenarios for immediate development handoff.