메뉴
Generate visual diagrams (flowchart, sequence, class, state, ER, C4) via draw.io. This skill should be used when the user says 'draw a diagram', 'visualize the architecture', 'create a flowchart', 'sequence diagram for X', 'show me the class hierarchy', or asks for any visual representation of code or systems.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.
QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.
Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.
Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.
Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.
Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.
| name | diagram |
| description | Generate visual diagrams (flowchart, sequence, class, state, ER, C4) via draw.io. This skill should be used when the user says 'draw a diagram', 'visualize the architecture', 'create a flowchart', 'sequence diagram for X', 'show me the class hierarchy', or asks for any visual representation of code or systems. |
| user-invocable | true |
| args | [{"name":"type","description":"Diagram type: flowchart, sequence, class, state, er, c4 (optional — auto-detected)","required":false},{"name":"subject","description":"What to diagram (optional)","required":false}] |
$ARGUMENTS for diagram type and subject