メニュー
Captures a bug, feature, or improvement as a clean, structured issue document. Invoke mid-flow when the user wants to log something without losing their current context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
System design skill for complex multi-component projects. Produces a system diagram, component breakdown, API contracts, data model, and tech decisions before any code is written. Run /architect before /createplan on anything that spans more than one layer (frontend + backend, multiple services, or a new data model).
Creates a structured implementation plan document. Invoke after /explore Q&A is complete and all ambiguities are resolved. Produces a markdown plan with steps, subtasks, key decisions, and risks.
Curates the owner's reference library at ~/.claude/references/repos.yaml. Each entry is a GitHub repo you find inspiring — patterns to copy, products to study, stacks to learn from. The skill ingests the repo's signal files (README, manifests, schemas, docs) into the local 'refs' ChromaDB collection so /cto and github-scout pull from YOUR curated taste, not generic GitHub search. Idempotent — re-running on an existing entry is safe.
Generates an exhaustive product-facing PRD with screens, features, flows, landing page mock, and visual direction. This is the artifact the operator reviews BEFORE any code is written. Output is both narrative (prd.md) and visual (lightweight HTML wireframes for every screen + landing page). Run after /grill (and /benchmark if competitive) and before /architect. The prd-reviewer agent must PASS before the user is brought in for manual review.
Produces an exhaustive feature matrix for a competitive product category BEFORE any PRD is written. Rows = atomic features, columns = competitors + you, cells = yes/no/partial with evidence. Forces "does product X do feature Y?" instead of prose summaries where features slip through. Run this before /grill, /architect, or any PRD work on a competitive product. Replaces lazy prose teardowns.
YC-style forcing questions before writing any code. Six questions that reframe the product, challenge bad assumptions, and surface the 10-star version. Run this before /architect or /createplan on any new product or major feature. Stops you from building the wrong thing.
| name | create-issue |
| description | Captures a bug, feature, or improvement as a clean, structured issue document. Invoke mid-flow when the user wants to log something without losing their current context. |
| argument-hint | ["brief description of the issue"] |
The user is mid-flow and wants to capture a bug, feature, or improvement fast. Turn their rough description into a clean, complete issue — quickly.
If the description gives you enough to work with, write the issue immediately. Don't ask questions for the sake of it. The user is mid-development and every back-and-forth costs them context.
If something critical is genuinely missing, ask — but max one round, max 2-3 questions, then write regardless of what you get back.
## [Type: Bug | Feature | Improvement | Chore] — [Title]
**Priority:** P0 (critical) | P1 (high) | P2 (normal) | P3 (low)
**Effort:** XS | S | M | L | XL
---
### What's happening / What's needed
[1-3 sentences. For bugs: what's broken. For features/improvements: what's missing or could be better.]
### Expected behaviour
[What should happen instead. Skip for chores.]
### Relevant files
- `src/path/to/file.ts` — [why it's relevant]
- *(max 3)*
### Notes / Risks
- [Edge cases, dependencies, rollback concerns. Skip if none.]
Type: Bug broken | Feature net new | Improvement existing could be better | Chore maintenance, no user impact
Priority: P0 blocking now | P1 high, next sprint | P2 normal backlog | P3 nice to have
Effort: XS under 1h | S half day | M 1-2 days | L 3-5 days | XL needs breaking down