aif-plan

Feature planning reduces ambiguity by loading project context to generate a branch name, define milestones, and create a structured implementation blueprint. This ensures development handoff is clear and aligned with roadmap milestones.

Generating a branch name and task plan from a feature request involves loading project context and prompting for preferences to structure the work. The output is a detailed plan file that records blocking factors and milestones for development.

Yes, you can align feature task planning with an existing project roadmap by integrating optional ROADMAP and RESEARCH contexts. This ensures generated task plans and branches match your defined milestones and research scope.

Yes, aif-plan supports both fast and full planning modes for feature startups. Fast mode quickly generates branch or patch plan outputs, while full mode creates a comprehensive implementation plan with blocking factors and milestones.

To create a plan file recording blocking factors for development handoff, run a full planning session on your feature description. This generates a branch-scoped plan file that explicitly documents blocking factors and milestones.

You should avoid using a branch-scoped implementation plan for task planning when your work lacks a specific feature description or requires no development handoff. The approach is designed for structured, roadmap-aligned feature work rather than unstructured requests.