--- name: sp-planning-34c42a87cce3 description: Use when the user asks for a concrete implementation plan for an agreed change before code is written. --- # Implementation Planning Write a plan that a skilled developer can execute without rediscovering the design. FlickNote is the single source of truth. ## 1. Explore Reality Before planning: - Read the relevant code, tests, docs, and repository rules. - Search prior work with `flicknote find `. - Map existing constraints, interfaces, dependencies, and failure modes. - Confirm the target repository. Do not design from filenames or assumptions. ## 2. Confirm the Approach Before writing the detailed plan, tell the user: - What exists now - The proposed approach and why - The main trade-off or risk Stop for explicit alignment if the direction has not already been approved. ## 3. Define the Plan Include: - Goal and anti-goals - Exit criteria expressed as observable behavior - Exact scope and files - Ordered implementation stages - Test strategy and exact verification commands - Risks, dependencies, and rollout concerns For behavior changes and bug fixes, plan a TDD sequence: 1. Add a focused test. 2. Run it and confirm the expected failure. 3. Implement the minimum change. 4. Run focused and broader tests. 5. Refactor only while green. Mechanical deletions, generated files, and configuration-only work do not need invented tests; state the appropriate verification instead. ## 4. Keep Scope Executable Split the plan into separate deliverable phases when: - Multiple repos can ship independently - A stage has a separate rollback boundary - The plan is too large to review or verify as one change Record dependencies between phases in the plan. Do not create tasks automatically. ## 5. Persist to FlickNote Create or update one note in the `orientation` project: flicknote add --project orientation flicknote detail --tree flicknote modify Use this structure: # Plan: ## Goal ## Anti-goals ## Current state ## Approach ## Implementation stages ## Test strategy ## Exit criteria ## Risks and dependencies Each stage must name the files, behavior change, tests, verification, and commit boundary when useful. ## Worker-Eye Check Re-read the saved note as the implementer: - Are paths and commands accurate? - Is each stage self-contained and ordered? - Are hidden assumptions written down? - Would execution require another design decision? - Is the scope small enough to deliver safely? Update the FlickNote note until the answers are clear. Return its ID and a concise summary. Stop; do not start implementation or invoke another skill. --- Source attribution: tta-lab Original project: https://github.com/tta-lab/ttal-cli/blob/3576d21f223ff97eb258b868553b6266ad393847/skills/sp-planning/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 GuionAI Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: tta-lab Original project: https://github.com/tta-lab/ttal-cli/blob/3576d21f223ff97eb258b868553b6266ad393847/skills/sp-planning/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management, Project & Program Management Roles: Backend Developer, Frontend Developer, Product Manager, Project Manager, Technical Product Manager Specialties: Specialty not specified Tools: Ttal Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: c08a84718fb2ee2b032622015c47c37a35a7c023eb77938e847da3383907454e