Plan - Implementation Planning

Shared project skill-context

Before mode routing or work, read existing files relative to the current project root in this order (reuse them if already loaded):

1. .ai-factory/skill-context/global-skill-context.md, all bundled skills.
2. .ai-factory/skill-context/build-skill-context.md, only fix, implement, plan, verify, improve.
3. .ai-factory/skill-context/aif-plan/SKILL.md, this skill.

Missing files are skipped; an existing unreadable file stops dependent work with its path. Precedence: individual > build (when applicable) > global > skill defaults; retain non-conflicting instructions and check all outputs against the effective rules. These layers customize workflow; they do not replace the project's rules/architecture hierarchy or relax explicit requirements, ownership, scope, safety/privacy, validation, or approval boundaries. Report conflicts with those boundaries instead of overriding them. global is a project-local layer, not home-directory configuration. Custom/extension skills do not automatically use it.

Create an implementation plan for a feature or task. Three modes:

• Fast, quick plan, no git branch, saves to the configured fast plan path (default: .ai-factory/PLAN.md)
• Full, richer plan, asks preferences, saves to the configured full-plan directory, and optionally creates a git branch/worktree when git is enabled and branch creation is allowed
• Ultra, exhaustive multi-file plan bundle under the configured full-plan directory: index.md is the manifest/progress ledger and every implementation phase is a separate, deeply specified markdown file. Use it when planning with a stronger model for later execution by a smaller model.

For ultra layout, detail requirements, integrity checks, and consumer behavior, read references/ULTRA-FORMAT.md before creating or modifying the bundle.

Runtime-aware questions

Apply this contract whenever the workflow asks the user to decide: