メニュー
Use when you have a spec or requirements for a multi-step task, before touching code. Produces comprehensive implementation plans with bite-sized tasks, exact file paths, complete code snippets, and test-first workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Usage: Build feature {spec-name} phase {phase-number}. Implements a single phase from the spec's task plan, iterating build-test cycles until the phase passes its constitution gate, then records memory, logs decisions, and commits.
Use this skill when the user asks to map, document, or onboard into an existing codebase. Produces structured documentation covering stack, structure, architecture, conventions, integrations, testing, and concerns. Only documents what is verifiable from files or terminal output — never infers or assumes.
Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design through collaborative dialogue before implementation.
Browser automation skill. Drives agent-browser through structured navigate→snapshot→interact→re-snapshot flows with authentication support, form automation, visual verification, and explicit human checkpoints for external flows.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes.
Systematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected.
| name | writing-plans |
| description | Use when you have a spec or requirements for a multi-step task, before touching code. Produces comprehensive implementation plans with bite-sized tasks, exact file paths, complete code snippets, and test-first workflow. |
Write comprehensive implementation plans assuming the engineer has zero context for the codebase. 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 the toolset or problem domain. Assume they don't know good test design very well.
Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
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]
---
Each task should follow this pattern:
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file`
- Modify: `exact/path/to/existing:123-145`
- Test: `tests/exact/path/to/test`
**Step 1: Write the failing test**
[Complete test code]
**Step 2: Run test to verify it fails**
Run: `cargo test <test-selector>`
Expected: FAIL with "[expected error message]"
(Adapt `<test-selector>` to the workspace test runner syntax.)
**Step 3: Write minimal implementation**
[Complete implementation code]
**Step 4: Run test to verify it passes**
Run: `cargo test <test-selector>`
Expected: PASS
**Step 5: Commit**
git add [files]
git commit -m "feat: add specific feature"
Generated by autoharness | Template: community/skills/writing-plans/SKILL.md.tmpl