aif-plan

Create structured implementation plans for new features in fast or full modes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ichinya/idshka --skill aif-plan-ichinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-plan
Source: https://github.com/ichinya/idshka/tree/main/.codex/skills/aif-plan
Command: npx skills add https://github.com/ichinya/idshka --skill aif-plan-ichinya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan teams with a lightweight process to convert feature requests into concrete tasks and templates that map to code changes and delivery milestones.

Core Features & Use Cases

  • Two planning modes: Fast for quick, minimal plans and Full for richer planning with optional git worktrees and branching.
  • Automatic plan templates, file paths for plan storage, and support for Roadmap and RESEARCH contexts to ground work.
  • Seamless handoff to implementation with optional commit checkpoints and mandatory or recommended docs checkpoints.

Quick Start

Describe a plan to implement a feature using the selected mode and generate the corresponding plan file.

Frequently Asked Questions about aif-plan

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

FAQPage Schema
How do I create a structured implementation plan for a new software feature?

To create a structured implementation plan, describe your feature request to generate a plan file using a consistent template. The system guides you from quick fast plans to richer full plans with optional git worktrees and roadmap linkage.

What is the difference between fast and full planning modes for project planning?

Fast mode generates quick, minimal plans for immediate action, while full mode produces richer planning that includes optional git worktrees, branching strategies, research context, and detailed task commits for incremental delivery.

Can I use git worktrees to isolate feature planning and development branches?

Yes, git worktrees are supported in full planning mode to isolate feature work and branching. This allows you to manage parallel development streams while maintaining structured plan templates and clear file paths for plan storage.

How do I link roadmap context and research documentation into task management plans?

You can link roadmap and research contexts to ground your plan by providing them as input during planning. The system integrates these contexts into the structured plan template, ensuring tasks map directly to documented milestones.

What's the best way to hand off a feature plan to the implementation phase?

The best way to hand off plans is through mandatory documentation checkpoints and optional commit checkpoints. This enforces consistent file paths and logging, streamlining the transition from planning to incremental code delivery.

Does this task management approach enforce documentation checkpoints during feature development?

Yes, the process enforces mandatory or recommended documentation checkpoints alongside optional commit checkpoints. This ensures incremental delivery maintains proper logging and consistent plan templates throughout the implementation lifecycle.