skills.rest
CornFedKratos
CornFedKratosCOMMUNITY
Explore all skills by this author →
GitHub

aidlc-writing-plans

Convert AIDLC specs into executable implementation plans with task breakdowns.

Updated Apr 11, 2026
Search Tags:#workflow#planning#documentation#task-breakdown#plan-generation#aidlc-specs
One-click install
npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-writing-plans-cornfedkratos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aidlc-writing-plans
Source: https://github.com/CornFedKratos/s3-aidlc/tree/main/plugins/s3-aidlc/skills/aidlc-writing-plans
Command: npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-writing-plans-cornfedkratos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams turn scattered AIDLC specs or requirements into a clear, executable implementation plan that can be reviewed and committed.

Core Features & Use Cases

  • Generate end-to-end task breakdowns from an AIDLC spec, mapping tasks to files, tests, and milestones.
  • Enforce plan structure with design decisions, validation steps, and versioned plan documents.
  • Save plans to the repository under docs/superpowers/plans with a date-based filename for traceability.

Quick Start

Turn an AIDLC spec into a concrete, plan-ready document by running the writing-plans workflow and saving the result to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md

Frequently Asked Questions about aidlc-writing-plans

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

FAQPage Schema
How do I turn AIDLC specs into an actionable implementation plan?▼

To turn AIDLC specs into an implementation plan, convert the requirements into an executable document featuring explicit task breakdowns, testing guidance, and commit-ready artifacts mapped to milestones.

How do I break down feature development tasks into files and tests?▼

Break down feature development tasks by generating an end-to-end structure that maps specific tasks directly to code files, testing guidance, and milestones for clear execution and validation.

What should an executable plan document include for feature development?▼

An executable plan document should include project scope, design decisions, validation steps, task breakdowns mapped to files, and testing guidance to ensure structured implementation.

How do I store versioned plan documents in my repository?▼

Store versioned plan documents in your repository by saving them under docs/superpowers/plans using a date-based filename format like YYYY-MM-DD-feature-name.md for traceability.

Can I use this workflow for features requiring explicit task breakdown?▼

Yes, this workflow is designed specifically for feature development requiring explicit task breakdown, structured design decisions, and validation steps across files, tests, and documentation.

Related Skills

Explore More Software Engineering Skills→
csackridercsackrider

plan

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

Community
Intermediate
FourthWizFourthWiz
2

implement

Convert development plans into tested code with commits and PRs.

Community
Advanced
donygeorgedonygeorge
2

plan

Generate milestone-driven implementation plans with testable exit criteria.

Community
Advanced
KhoiwallKhoiwall

writing-plans

Generates detailed bilingual meeting summaries and to-do lists from raw text or audio transcripts.

Community
Advanced