メニュー
Write implementation plans with appropriate templates based on complexity. Use when planning features or changes. Provides minimal, standard, and full templates for different scope levels.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications. Includes framework-specific guidance for Tailwind, React, Vue, and Rails/Hotwire ecosystems.
Skill file structure, naming conventions, directory layout, frontmatter requirements, and invocation control. Use when creating skill files or slash commands to ensure correct format and validation.
Forces adversarial reasoning before committing to decisions. Triggers on architectural choices, approach selection, and planning phases to prevent premature commitment bias.
Verify LLM reasoning using Reverse Chain-of-Thought (RCoT) to detect overlooked conditions.
Autonomous task implementation - research, plan, build, review, fix, ship
Generate a complete favicon set (ICO, PNG variants, apple-touch-icon, web manifest) from a source image and integrate into the project's HTML layout. Use when user asks to generate favicons, set up PWA icons, or add an apple-touch-icon.
| name | plan-builder |
| description | Write implementation plans with appropriate templates based on complexity. Use when planning features or changes. Provides minimal, standard, and full templates for different scope levels. |
| allowed-tools | Read Write Edit |
Write implementation plans using the appropriate template based on complexity.
| Complexity | When to Use | Template |
|---|---|---|
| Minimal | Simple bugs, small improvements, clear single-file changes | references/minimal.md |
| Standard | Most features, complex bugs, team collaboration | references/standard.md |
| Comprehensive | Major features, architectural changes, multi-phase work | references/comprehensive.md |
Write plans to: docs/plans/[YYYYMMDDHHMMSS]_<title>.md
Include in every plan:
src/models/user.rb:42)Include "Design System Reference" section when feature involves:
Include "Infrastructure Context" section when feature involves:
| Don't | Do |
|---|---|
| Use comprehensive for simple bugs | Match template to actual complexity |
| Skip Acceptance Criteria | Always include testable criteria |
| Leave placeholder text | Fill all sections or remove them |
| Over-plan obvious changes | Minimal template exists for a reason |