メニュー
Implement features incrementally through vertical slices. Use when building features, adding functionality, or implementing tasks that touch multiple files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.
Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.
Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.
Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.
Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.
Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.
| name | build |
| description | Implement features incrementally through vertical slices. Use when building features, adding functionality, or implementing tasks that touch multiple files. |
Build in thin vertical slices. Implement one piece, verify it, commit it, then move on. Never accumulate uncommitted work across multiple slices.
Before the first slice, if not already on a dedicated branch, create one. Consider an isolated worktree (git worktree add -b <topic> .claude/worktrees/<topic>) so the main session stays an orchestrator. Never use git -C <path> — always cd into the target first.
A slice is one path, not one layer. Good: POST /orders endpoint + the form that calls it + one test. Bad: all endpoints, then all UI, then all tests.
plan for scope and phase boundariestdd for red-green-refactor within each slice