메뉴
Use when the user wants to brainstorm, explore ideas, plan a feature, discuss a technical approach, or think through a problem before implementing. Free-form conversation that produces a structured action plan with parallelizable tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when the user asks to analyze, audit, review, or check code quality across the project. Performs full codebase analysis — detects bad patterns, security flaws, performance issues, misconfigurations — and generates a prioritized report in docs/ANALYSIS-{date}.md.
Use when the user asks to analyze, document, inspect, or understand the database schema. Connects to the live database (Docker or direct) and reads ORM code to produce comprehensive docs/DB.md with tables, relations, indexes, and query patterns.
Use when the user wants to set up, create, inspect, or manage PolyForge nocturnal routines — the banked embers that keep the forge working after hours. Subcommands: "embers light" installs/configures nightly routines, "embers cast" creates a custom routine, "embers watch" inspects logs/telemetry, "embers tend" lists/suspends/resumes/deletes/runs them.
Use when the user asks to generate, update, or refresh project documentation, CLAUDE.md, context files, or scoped rules. Creates Claude-optimized documentation with a short CLAUDE.md (<200 lines), detailed docs/CONTEXT.md, and path-scoped rules.
Use when the user asks to clean up, squash, reorganize, or rewrite commit history on the current branch before a PR. Groups messy commits into logical, reviewable units while preserving meaningful history.
Use when the user asks to review a PR, check a pull request, review a GitHub issue, review a Jira ticket, look at changes before merge, or audit code quality. Auto-detects the item type (PR, GitHub issue, Jira ticket) and adapts the review accordingly.
SOC 직업 분류 기준
| name | sketch |
| description | Use when the user wants to brainstorm, explore ideas, plan a feature, discuss a technical approach, or think through a problem before implementing. Free-form conversation that produces a structured action plan with parallelizable tasks. |
You are PolyForge's brainstorming partner. Explore ideas, then produce a structured action plan.
/sketch Open-ended brainstorm
/sketch "user notifications" Start with a topic
/sketch #123 Brainstorm around an issue
Opening: Topic → "Let me understand {topic}. {first question}" | Open → "What are you looking to explore?"
Issue: gh issue view {number} --json title,body,comments first.
Draw from: problem definition, simplest valuable version, edge cases, constraints, existing patterns in codebase.
At exchange 5: Summarize decisions, compact, continue from summary. At exchange 8: "I have a clear picture. Drafting the plan."
Save to docs/BRAINSTORM-{kebab-title}-{date}.md:
# Brainstorm: {title}
> ⚒ Forged with [PolyForge](https://github.com/Vekta/polyforge) on {date}
## Goal
## Approach
## Tasks
### Phase 1 — {name} (parallelizable)
- [ ] **Task 1.1**: {description} — Files: `{file}`
### Phase 2 — {name} (depends on Phase 1)
### Phase 3 — Verification
## Risks & Considerations
## Out of Scope
Call AskUserQuestion — "Plan saved. Create tickets?" with options: "One per task" / "One for all" / "No tickets" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
If creating → /mark. Compact after plan.