aif-plan

Generate executable task plans and structured plan artifacts for software features.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-plan-exsydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-plan
Source: https://github.com/ExsyDev/eye-blinking/tree/main/.claude/skills/aif-plan
Command: npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-plan-exsydev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning software features end-to-end is often manual, scattered, and error-prone. This Skill automates implementation planning by generating executable task plans and structured plan artifacts.

Core Features & Use Cases

  • Two modes: fast (no branch) and full (git branch + plan).
  • Generates phased task plans and plan files (.ai-factory/PLAN.md or .ai-factory/plans/<branch>.md).
  • Supports optional Roadmap linkage when ROADMAP.md exists, and optional Research Context from RESEARCH.md.
  • Enforces plan templates, logging preferences, and documentation checkpoints to ensure consistent governance.

Quick Start

Describe the feature you want to plan, or run /aif-plan full to start a comprehensive planning workflow.

Frequently Asked Questions about aif-plan

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

FAQPage Schema
How do I automate software feature planning with structured task plans?

Automating software feature planning generates executable task plans and structured plan artifacts like .ai-factory/PLAN.md. It produces phased task plans end-to-end, ensuring consistent governance through enforced templates, logging preferences, and documentation checkpoints.

What is the difference between fast and full modes for generating a feature implementation plan?

Fast mode generates an implementation plan without creating a git branch, while full mode creates a git branch and saves the plan to plans/<branch>.md. Both modes produce structured plan artifacts but full mode integrates deeper version control context.

Can I link my implementation task plan to an existing roadmap?

Implementation task plans support optional Roadmap linkage when a ROADMAP.md file exists in the project. The planning workflow automatically integrates this roadmap context to align generated tasks with broader project milestones and goals.

Do I need a git branch to plan software features and generate plan files?

You do not need a git branch to plan software features. The fast mode generates a plan artifact directly without branching, while full mode initializes a git branch and saves the structured plan file to .ai-factory/plans/<branch>.md.

How do I incorporate research context into feature planning and task generation?

Feature planning integrates optional Research Context automatically by reading from a RESEARCH.md file when present. This feeds existing research directly into the generated executable task plans, ensuring the implementation roadmap reflects prior technical findings.

What are the limitations of using templates for implementation planning?

Implementation planning enforces plan templates and documentation checkpoints to ensure consistent governance, which limits flexibility in deviating from the structured format. The workflow produces fixed plan artifacts like PLAN.md and requires specific context files for optional features.