メニュー
Create or update GitHub issues. Enforces self-contained issues that an Agent can implement without conversation Context. Use when the Architect says "create an issue", "file an issue", "gh issue", "update the issue", or wants to turn a Plan into a trackable issue.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Broad-to-narrow research Orchestration - start with a wide census, harden the scope from returned Evidence, and specialize Subagents only once the exact situation is proven. TRIGGER when the Architect says "progressive research", "start broad", or when dispatching research or debugging Subagents into a situation whose cause or shape is unknown. DO NOT TRIGGER when the exact scope is already proven - dispatch the specialized Subagent per /subagents directly.
Consolidate the knowledge wiki — revisit journaled topics, fold repeated findings into each topic's Claude.md, surface contradictions, keep cross-links true. TRIGGER on a scheduled pass or when a topic tree has grown messy or redundant. DO NOT TRIGGER to file fresh session material (that is journal), or to gather new research.
File a session's loose material into the knowledge wiki — each capture into its owning topic folder, the topic's Claude.md kept current. TRIGGER after a session hands you loose captures (notes, clippings, findings, screenshots) that need a home in the wiki. DO NOT TRIGGER to gather new research, or to consolidate the wiki itself (that is dream).
Operate Dent via first-party API. Trigger: Dent API, Funnels, Offers, Pages, Articles, Courses, Spaces, Analytics. Do not trigger for WordPress-only work.
Autonomous async Execution. The Architect hands off and walks away; the Agent drives the Task to done — makes every Architectural call via /trace + /pcc + ranking, executes through /subagents, verifies from each implementing Subagent's Evidence (they exercise their own flows, real browser for UI), and returns finished code plus the recorded Decisions for review. TRIGGER when the Architect says "code-first", "/code-first", "execute with /subagents", "execute directly & autonomously", "drive it and report back", "iterate until done", "I'm going to bed", "off to bed", or signals an AFK / overnight handoff. DO NOT TRIGGER when the Architect wants options before action — that is the default mode (propose via /pcc and wait).
| name | gh-issue |
| description | Create or update GitHub issues. Enforces self-contained issues that an Agent can implement without conversation Context. Use when the Architect says "create an issue", "file an issue", "gh issue", "update the issue", or wants to turn a Plan into a trackable issue. |
Read the affected code, check the nearest Claude.md for Rules the implementing Agent must follow, and gather repo-relative file paths.
Describe only code already read in this Task.
Name the file path the Agent can open.
Never: the config file, the auth module, or the usual place.
Inline the conversation's Plan or content. Include WHY, repo-relative file paths, concrete implementation detail, and acceptance criteria.
The body never points back to conversation Context, external files, Plans, or Shaping. It carries the needed content itself.
Never: see above, as discussed, see the shaping doc, or see the Plan file.
Ask whether an Agent can implement the issue without asking a single question.
IF the body is missing WHY, repo-relative paths, inline content, or acceptance criteria:
Do not run gh issue create or gh issue edit until the body is self-contained.
Run gh issue create, always pass --assignee @me, pass --repo <owner/repo> or --label when specified, then report the issue URL.
Template:
gh issue create --assignee @me --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
Use gh issue edit when the body, title, labels, or state changes. Every edit gets a gh issue comment stating WHAT changed and WHY. Body rewrites go through step 3 before editing.
The comment makes the changed issue self-contained for the next Agent.
Template:
gh issue edit <number> --body "$(cat <<'EOF'
<updated body>
EOF
)"
gh issue comment <number> --body "$(cat <<'EOF'
## Changes
- <WHAT changed>
WHY: <WHY these changes were necessary>
EOF
)"
gh issue close <number> --comment "Resolved: <reason>"