writing-plans
Writing Plans
Overview
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Context: This should be run in a dedicated worktree.
- Delegate worktree creation/switching to
worktree-manager. - Default intent: the worktree should copy the current working state so the plan can be executed without disturbing the original workspace.
Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
Bite-Sized Task Granularity
More from jtsang4/efficient-coding
brainstorming
Use only when the user explicitly asks to do brainstorming (e.g., says 'brainstorm'/'头脑风暴' or invokes $brainstorming). Do not auto-trigger based on general creative work.
17dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
13subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
13executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
12shape
>
11systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
11