skills.rest
Conava
ConavaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan

Generate a phased TDD implementation plan from a feature spec.

2|Updated Mar 11, 2026
Search Tags:#automation#planning#TDD#plan#phases#software#feature-spec
One-click install
npx skills add https://github.com/Conava/claude-devline --skill plan-conava
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Conava/claude-devline/tree/main/skills/plan
Command: npx skills add https://github.com/Conava/claude-devline --skill plan-conava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launching a reliable planning workflow that converts a feature spec into a structured, multi-phase implementation plan, reducing miscommunication and planning cycles.

Core Features & Use Cases

  • Launches a planner agent in the foreground from a feature specification.
  • Supports an interactive NEEDS_INPUT loop to resolve design choices, code issues, and improvements before finalizing the plan.
  • Produces a write-ready plan at .devline/plan.md (single-phase) or .devline/plan-phase-N.md (multi-phase) for later implementation.
  • Designed for integration into multi-phase pipelines with prior phase context to scope work.

Quick Start

Feed the feature specification to the planner and run it to generate a ready-to-approve plan at .devline/plan.md.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a feature spec into a TDD implementation plan?▼

To turn a feature spec into a TDD implementation plan, you feed the specification to a planner agent, which generates a structured, multi-phase plan at .devline/plan.md or .devline/plan-phase-N.md for later implementation.

What is the best way to handle design decisions during software planning?▼

Handling design decisions during software planning is managed through an interactive NEEDS_INPUT loop, allowing you to resolve code issues and design choices before finalizing the phased plan.

Can I scope work for multi-phase pipelines using prior phase context?▼

Yes, you can scope work for multi-phase pipelines by providing prior phase context to the planner, which then generates execution-ready phase outputs like .devline/plan-phase-N.md.

Does the planning workflow support interactive questions before finalizing the plan?▼

Yes, the planning workflow supports interactive questions through a NEEDS_INPUT cycle, enabling you to address improvements and design choices iteratively before the final plan is written.

Where are the generated implementation plans written?▼

Generated implementation plans are written directly to .devline/plan.md for single-phase outputs or .devline/plan-phase-N.md for multi-phase outputs, making them ready for immediate execution.

Related Skills

Explore More Software Engineering Skills→
nixlimnixlim

plan-spec

Generates structured feature specifications and implementation plans from briefs with traceability matrices.

Community
Advanced
giovannimnzgiovannimnz

gsd-plan-phase

Generate a phase execution plan with objectives, dependencies, and verification criteria.

Community
Advanced
CENKSSSCENKSSS

shift-left-testing

Validate requirements and generate tests before coding in CI/CD pipelines.

Community
Advanced
abrahamgreysonabrahamgreyson

gsd:workflow:verify-phase

Automate GSD workflow phase verification and quality standard checks.

Community
Intermediate