aif-plan

Plan feature implementations with structured tasks and optional Git branching.

56|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/lee-to/ai-workspace --skill aif-plan-lee-to
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-plan
Source: https://github.com/lee-to/ai-workspace/tree/main/.claude/skills/aif-plan
Command: npx skills add https://github.com/lee-to/ai-workspace --skill aif-plan-lee-to

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan feature implementations with structured tasks and optional Git branching. This Skill helps teams translate vague feature ideas into concrete implementation plans, delivering a clear path from concept to fenced tasks and Git branches.

Core Features & Use Cases

  • Two modes: Fast (no branch) and Full (git branch with a detailed plan)
  • Generates plan documents and task lists that map to code changes and milestones
  • Supports optional Roadmap and Research contexts, and configurable settings for testing, logging, and docs checkpoints

Quick Start

Run /aif-plan full Add user authentication to start planning.

Frequently Asked Questions about aif-plan

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

FAQPage Schema
How do I plan feature implementations with structured tasks and Git branches?

You can plan feature implementations by generating structured task lists and optional Git branches. This process creates plan artifacts mapping to code changes, supporting configurable testing, logging, and documentation checkpoints across multiple branches.

What is the best way to break down a feature idea into a development roadmap?

The best way to break down a feature idea is to generate plan documents and task lists that map to code changes and milestones. Using configurable settings for testing, logging, and docs ensures context-aware planning across multiple branches.

Can I use this to create a Git branch specifically for feature planning?

Yes, Full mode creates a Git branch specifically for feature planning. It generates a detailed plan with structured tasks, roadmap contexts, and configurable checkpoints for testing, logging, and documentation.

Do I need Git to generate a task list for my feature plan?

No, Git is not required to generate a task list for your feature plan. Fast mode operates without branching to quickly deliver plan artifacts and structured task breakdowns, while Full mode adds Git branch integration.

How do configurable settings apply to feature planning and task breakdowns?

Configurable settings apply to feature planning by adding checkpoints for testing, logging, and documentation within task breakdowns. This ensures generated plan artifacts and roadmaps align with specific project requirements and quality standards.

When should I choose Full mode over Fast mode for planning a feature?

Choose Full mode when your feature requires a Git branch with detailed plan artifacts, roadmaps, and research contexts. Fast mode suits quick task list generation without branching overhead.