What problem does it solve? Non-trivial coding tasks handled without a written plan lead to wasted effort, uncoordinated subagents, and unintended breaking changes. This Skill enforces a mandatory research-plan-approve-execute-verify lifecycle so multi-file and cross-layer work is documented, user-approved, and verifiable before any file is edited. ## Core Features & Use Cases - Five-Phase Lifecycle: Research (read-only), write the plan, obtain explicit user approval, execute with progress tracking, and verify with builds, tests, and a walkthrough document. - Shared Plans Repository Protocol: Stores plans in a versioned <organization>/<repository>/YYYY-MM-DD/task_name/ layout with strict _v<N> versioning, document-set harmonization, an allowed-organization allowlist, and a gitignored .plans/ or chat-only fallback tier. - Commit and Push Discipline: Permits git commit/push only in the plans repository, with explicit-path staging, rebase-based conflict recovery, and a ban on committing in any project repository. - Use Case: An agent asked to add SSO login across a backend and client SPA writes implementation_plan_v1.md under hyvanmielenpelit/GnollHack/2025-01-15/sso_login/, waits for approval, executes with subagents, then produces task.md and walkthrough.md with verification results. ## Quick Start Ask the agent to create an implementation plan for your multi-file feature before it edits any code, and approve the plan document it links to you.
