af-sdlc-plan

Analyze a repository and generate milestone-based implementation plans with file-level changes.

1|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/e-stpierre/agentic-forge --skill af-sdlc-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-sdlc-plan
Source: https://github.com/e-stpierre/agentic-forge/tree/main/src/claude/.claude/skills/sdlc-plan
Command: npx skills add https://github.com/e-stpierre/agentic-forge --skill af-sdlc-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a repeatable way to turn a task description or issue into a concrete, scoped implementation plan with milestones, actionable tasks, file-level guidance, and validation steps so engineering teams can execute work in isolated sessions without ambiguity.

Core Features & Use Cases

  • Codebase Analysis & Scoping: Identifies relevant files, patterns, and impact areas and maps dependencies to ensure changes are correctly targeted.
  • Type-Specific Planning: Produces feature, bug, or chore plans using tailored guidance and templates, including reproduction steps, root cause analysis, or scope definition.
  • Milestone-Driven Delivery: Breaks work into session-scoped milestones that produce concrete outputs, with testing and validation checklists for each milestone. Use cases include preparing feature implementation plans, structuring bug fix work with reproduction and tests, and organizing maintenance chores like dependency upgrades.

Quick Start

Ask the skill to create a feature plan for "Add OAuth login with GitHub" and save the plan to the default outputs directory.

Frequently Asked Questions about af-sdlc-plan

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

FAQPage Schema
How do I create an implementation plan from a task description?

To create an implementation plan, analyze the repository to identify relevant files and map dependencies, then produce milestone-based tasks. This approach breaks work into session-scoped milestones with file-level changes, testing guidance, and validation steps.

What's the best way to structure bug fix work with reproduction steps and tests?

The best way to structure bug fix work is using type-specific planning that includes reproduction steps, root cause analysis, and validation checklists. This produces milestone-driven plans that target relevant files and map dependency impact.

How does codebase analysis identify relevant files for an implementation plan?

Codebase analysis identifies relevant files, patterns, and impact areas by mapping dependencies to ensure changes are correctly targeted. This ensures the implementation plan accurately scopes the necessary file-level modifications.

Can I use milestone-based task decomposition for dependency upgrade chores?

Yes, you can use milestone-based task decomposition for maintenance chores like dependency upgrades. It structures work into session-scoped milestones with concrete outputs, applying tailored scope definition and validation checklists for each phase.

Does this planning approach handle feature, bug, and chore scenarios differently?

Yes, this planning approach produces feature, bug, or chore plans using tailored guidance and templates. Feature plans define scope, bug plans include reproduction steps, and chore plans organize maintenance work into actionable milestones.

What are the limitations of milestone-driven delivery for complex codebases?

Milestone-driven delivery breaks work into session-scoped milestones that produce concrete outputs. If a complex codebase requires cross-milestone dependency tracking beyond file-level changes, manual coordination may be needed outside the generated markdown plan.