Menu
Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Preserve project architecture and SOLID when proposing or writing code. Always identify the correct layer and minimal design first.
Explore and shape a new feature before code generation. Always determine architectural placement, design options, trade-offs, and recommended approach first.
Diagnose runtime and launch issues that happen only on physical iPhone devices. Always plan first, then wait for approval before changing code.
Diagnose and repair Kotlin Multiplatform + Swift build failures. Always plan first, wait for confirmation, then apply minimal fixes.
Format a GitHub (or GitLab) issue Summary for the feature-planner and later phases after gh issue view.
Structure a manual feature or bug report before feature-planner when not starting from a GitLab issue.
| name | workflow-plan-output |
| description | Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan. |
The feature-planner subagent owns the planning phase. Plans must be architecture-safe and file-oriented.
composeApp paths)Do not duplicate full templates here—use write-implementation-plan/plan-template.md for the question list.