plan

Orchestrate product-spec creation for AIDLC feature work with human approval.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/csackrider/AI-DLC --skill plan-csackrider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/plan
Command: npx skills add https://github.com/csackrider/AI-DLC --skill plan-csackrider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan phase orchestrates the creation of structured product specs for feature work within the AIDLC, ensuring human oversight and clean handoffs to design.

Core Features & Use Cases

  • Guided, conversation-first drafting of feature/product specs that require human approval.
  • Template-assisted generation of product-spec artifacts (feature slug, outcomes, success criteria) and handoff to /design.
  • Traceable decisions and handoffs aligned with AIDLC workflows.

Quick Start

Ask in chat for a feature slug and start the orchestration to draft a product-spec that moves to design after approval.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I draft a product spec for a new feature with human-in-the-loop approval?

Product spec creation uses a conversation-first workflow that guides feature artifact generation using templates, then requires explicit human approval before design handoff.

What is the best way to orchestrate product spec creation for feature development?

Product spec orchestration uses a structured workflow that drafts the spec, captures stakeholder input, records decisions, and manages artifact generation for clean design handoffs.

Can I require stakeholder approval before handing off a product spec to design?

Yes, requiring stakeholder approval before design handoff is enforced by this workflow, ensuring human oversight and traceable decisions are recorded during product spec creation.

Does the product spec workflow apply to specific feature slugs or general work items?

The product spec workflow applies specifically to feature work items under the feature/<slug>/ path, generating artifacts like feature slugs, outcomes, and success criteria.

How do I start the product spec planning workflow?

Start the product spec planning workflow by asking in chat for a feature slug, which initiates the orchestration to draft the spec and move it to design after human approval.