メニュー
Use when the user asks to write a plan for a multi-step task, before touching any code
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | writing-plans |
| description | Use when the user asks to write a plan for a multi-step task, before touching any code |
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."
Each step is one action (2-5 minutes):
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
Explains how packages are built in this monorepo. Use when working on build configuration, tsup config, package exports, or troubleshooting build issues.
Branch naming, changeset authoring, and PR conventions for this monorepo. Use when creating branches, committing, writing changesets, opening PRs, or running pre-merge checks.
How to version and publish packages to npm from the main branch. Use when running release commands, publishing to npm, or troubleshooting publish issues. For changeset authoring and PR prep, use the contributing skill instead.
Remove AI-generated code slop and clean up code style. Use when finalizing a PR.