Menu
Create a PLANS.md execution plan document for project management
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generic thinking protocol for deriving optimal solutions through iterative self-checking. Invoke BEFORE searching within the given problem space whenever the user asks for advice, judgment, evaluation, or choice. Reframes the problem, generates options, evaluates trade-offs, runs a self-answer check (does this answer the user's actual question at the right granularity, reach upstream, match expectations, offer non-obvious value?), and loops back to upstream tracing or same-level reframing if the check fails — until convergence. Applies across any domain — technical, process, organizational, decision-making, career. Triggers when the user uses evaluation or reconsideration language ("which is best", "root cause", "is this really needed", "sustainable long-term", "ほんとうに", "そもそも", "最善は", "根本は", "筋が良い"), when validating the soundness of someone's proposal from multiple perspectives, when the problem spans multiple layers (tech / process / org / regulation / UX / cost), or when clear trade-offs exist.
Review the local diff with flat-perspective sub-agents, fix findings in a loop, then create a PR via the create-pr skill once the review is clean
計画や設計について、ユーザーを徹底的に問い詰めて一緒に詰める。実装・着手の前に計画をストレステストしたいとき、または「詰めて」「グリルして」「問い詰めて」「ツッコんで」「設計レビューして」「ほんとうにこれでいい?」などのトリガー表現が出たときに必ず使う。
.claude/rules/ 配下のルールファイル (*.md) を新規作成・編集するときに、適切なメカニズム選択と paths スコープを保証する。ルールを書く前・書いた後に必ず適用する。
Orchestrate Epic issue as team leader. Delegate sub-issues to member agents in isolated worktrees. Members run in background and communicate via SendMessage.
Fetch a GitHub issue with its sub-issues, walk up to the parent Epic, list sibling issues under that Epic, fetch the body of each sibling issue, attach the implementing PR for each closed sibling with body and diff summary, gather related code, and present as a Japanese summary so the reader can grasp the whole task context including the actual contents of siblings and their PRs
| name | create-plan |
| description | Create a PLANS.md execution plan document for project management |
| disable-model-invocation | true |
プロジェクトルートに、実行計画を管理するための PLANS.md を作成する。
受け付ける入力:
123 または #123)$ARGUMENTS
引数が GitHub Issue を参照している場合:
#123, 123, または GitHub URL)gh issue view <issue-number> --json number,title,body,url で Issue を取得するIssue と紐づく PLANS.md を作る際は、以下のフロントマターを先頭に追加する:
---
issue: 123
issue_url: https://github.com/owner/repo/issues/123
last_synced: 2025-11-12T10:30:00Z
---
issue: Issue 番号issue_url: Issue の完全な GitHub URLlast_synced: 最終同期日時 (ISO 8601)。date -u +"%Y-%m-%dT%H:%M:%SZ" で生成Purpose / Overview
Context & Direction
Validation & Acceptance Criteria
Specification
Open Questions
Discoveries & Insights
Decision Log
Outcomes & Retrospectives
Follow-up Issues
- [ ]) を使うIssue フロントマター付き PLANS.md を作成したら、Issue にコメントを投稿する:
gh repo view --json owner,nameTIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
CONTENT="<!-- PLANS_SYNC_MARKER:${TIMESTAMP} -->
$(tail -n +5 PLANS.md)" # Skip frontmatter (lines 1-4)
gh issue comment <issue-number> --body "$CONTENT"
同期マーカーの形式: <!-- PLANS_SYNC_MARKER:2025-11-12T10:30:00Z -->
これにより、/sync-plan が後からこのコメントを発見・更新できるようになる。