Skip to content

unxed/f4 / .agents/skills/aif-plan

aif-plan

Verified

Plan a feature or task in fast, full, or ultra mode. Ultra creates an indexed multi-file bundle with deeply specified phases for execution by a smaller model. Use for "plan", "new feature", "start feature", "create tasks", or exhaustive implementation planning.

FileKindSize
SKILL.mdskill md49.5 KB
references/EXAMPLES.mdmarkdown5.2 KB
references/TASK-FORMAT.mdmarkdown5.0 KB
references/ULTRA-FORMAT.mdmarkdown7.4 KB

references/EXAMPLES.md

View on GitHub
# aif-plan Examples

## Argument Parsing

### Fast mode explicit

```text
/aif-plan fast Add product search API
-> mode=fast, description="Add product search API"
```

### Full mode explicit

```text
/aif-plan full Add user authentication with OAuth
-> mode=full, description="Add user authentication with OAuth"
```

### Ultra mode explicit

```text
/aif-plan ultra Rebuild billing around an immutable ledger
-> mode=ultra, description="Rebuild billing around an immutable ledger"
```

### Full mode with description omitted (defaults from RESEARCH.md)

```text
/aif-plan full
-> mode=full
-> description defaults to .ai-factory/RESEARCH.md Active Summary Topic (if present)
```

### Full mode with parallel worktree

```text
/aif-plan full --parallel Add Stripe checkout
-> mode=full, parallel=true, description="Add Stripe checkout"
```

### List subcommand

```text
/aif-plan --list
-> show worktrees, STOP
```

### Cleanup subcommand

```text
/aif-plan --cleanup feature/user-auth
-> remove worktree, STOP
```

### No mode provided

```text
/aif-plan Add user authentication
-> ask full/fast interactively, description="Add user authentication"
-> ultra is not shown or inferred; it requires the explicit leading token
```

### No mode + no description (defaults from RESEARCH.md)

```text
/aif-plan
-> ask mode interactively
-> description defaults to .ai-factory/RESEARCH.md Active Summary Topic (if present)
```

## Flow Scenarios

### Scenario 1: Fast mode

```text
/aif-plan fast Add product search API

-> mode=fast
-> Asks about tests (No)
-> Explores codebase
-> Creates 4 tasks
-> Saves plan to `paths.plan` (default: `.ai-factory/PLAN.md`)
-> STOP
```

### Scenario 2: Full mode (normal)

```text
/aif-plan full Add user authentication with OAuth

-> mode=full
-> Quick reconnaissance
-> Plan slug: user-authentication
-> Branch: feature/user-authentication (if git branch creation is enabled)
-> If ROADMAP.md exists: asks about milestone linkage, user picks one (or skips)
-> Asks about tests (Yes), logging (Verbose), docs (Yes)
-> Creates branch only when `git.enabled=true` and `git.create_branches=true`
-> Explores codebase deeply
-> Creates 8 tasks with commit checkpoints
-> Saves plan to `paths.plans/feature-user-authentication.md` (or `paths.plans/user-authentication.md` when no branch is created)
-> When `workflow.plan_id_format = sequential`, the filename gains a 4-digit prefix:
   `paths.plans/0007_feature-user-authentication.md`
-> STOP - user runs /aif-implement when ready
```

### Scenario 3: Full mode (parallel)

```text
/aif-plan full --parallel Add Stripe checkout

-> mode=full, parallel=true
-> Quick reconnaissance
-> Branch: feature/stripe-checkout
-> If ROADMAP.md exists: asks about milestone linkage, user picks one (or skips)
-> Asks about tests (No), logging (Verbose), docs (No)
-> Creates worktree ../my-project-feature-stripe-checkout
-> Copies context files, cd into worktree
-> Explores codebase deeply
-> Creates 6 tasks
-> Saves plan to `paths.plans/feature-stripe-checkout.md`
-> Auto-invokes /aif-implement (parallel = autonomous)
```

### Scenario 4: Interactive mode selection

```text
/aif-plan Add user authentication

-> No mode keyword found
-> Asks: Full (Recommended) or Fast?
-> User picks Full
-> Continues as full mode flow
```

### Scenario 5: Full mode with sequential numbering (`plan_id_format: sequential`)

```text
.ai-factory/plans/ already contains:
  0001_admin-auth.md
  0002_admin-design.md
  0003_admin-bootstrap.md

/aif-plan full Add user authentication with OAuth

-> mode=full
-> workflow.plan_id_format = sequential (resolved from .ai-factory/config.yaml)
-> Plan slug: user-authentication
-> Branch:    feature/user-authentication        # branch stays un-numbered
-> Next number: max(0001, 0002, 0003) + 1 = 0004 → "0004"
-> Saves plan to paths.plans/0004_feature-user-authentication.md
-> STOP - user runs /aif-implement when ready

# If the directory is empty, the same flow starts from 0001.
# Numbers are derived from existing files: deleting 0004_*.md frees the 0004
# slot, and the next /aif-plan run will reuse it. Keep prior plans in place
# if you rely on stable cross-references.
# When HANDOFF_BRANCH_PREPARED=1, sequential numbering is force-disabled and
# the filename equals the branch name (Handoff contract).
```

### Scenario 6: Ultra mode

```text
/aif-plan ultra Rebuild billing around an immutable ledger

-> mode=ultra
-> Performs full preferences and optional branch setup
-> Deeply maps current billing models, callers, persistence, tests, and operations
-> Resolves plan identifier: feature-rebuild-billing
-> Creates:
   paths.plans/feature-rebuild-billing/
     index.md
     phase-01-ledger-domain.md
     phase-02-persistence-migration.md
     phase-03-service-integration.md
     phase-04-rollout-and-observability.md
-> index.md owns Original Request, settings, research/roadmap context,
   phase table of contents, task checkboxes, dependencies, and commit plan
-> Every phase file contains exact paths/symbols, ordered edits, contracts,
   error/logging behavior, test policy, acceptance criteria, and verification
-> STOP - user can clear context and run /aif-implement with the bundle

# With workflow.plan_id_format=sequential, the directory would be:
# paths.plans/0007_feature-rebuild-billing/
```
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall