Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for automation.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Classify issues with a formal state machine. ready-for-agent is the handoff trigger to the supergraph pipeline.
Announce: "🗂️ /supergraph:triage — classifying issues..."
needs-triage
├── enough info → [assign category] → ready-for-agent | ready-for-human
└── missing info → needs-info → [info provided] → ready-for-agent | ready-for-human
ready-for-agent → supergraph:plan pipeline
ready-for-human → manual dev / architectural decision needed
wontfix → closed with reason
| Category | When |
|---|---|
bug | Observed behavior differs from specified behavior |
enhancement | New capability or improvement to existing behavior |
question | Needs clarification before any action |
spike | Research / proof-of-concept, no production code |
| State | Meaning |
|---|---|
needs-triage | Unreviewed — default for new issues |
needs-info | Blocked on missing information from reporter |
ready-for-agent | Fully specified — safe for /supergraph:plan to consume |
ready-for-human | Needs human judgment (architecture, business decision, security) |
wontfix | Will not be addressed — reason required |
1. Read the issue completely.
2. Assign category — bug / enhancement / question / spike.
3. Check readiness for agent:
A bug is ready-for-agent when:
An enhancement is ready-for-agent when:
If NOT ready → set needs-info and list exactly what's missing (one question per response).
4. Assign state and apply labels via GitHub CLI:
gh issue edit <number> --add-label "bug,needs-info"
gh issue edit <number> --add-label "enhancement,ready-for-agent"
gh issue edit <number> --add-label "wontfix"
# Add comment explaining state change:
gh issue comment <number> --body "Triage: [reason for state]"
5. For ready-for-agent issues — summarize for plan intake:
Issue #N: [title]
Category: bug | enhancement
Acceptance: [1-3 criteria]
Constraints: [any known]
→ /supergraph:plan
For a backlog of issues:
gh issue list --state open --label "needs-triage" --json number,title,body
Process each in order. Report counts at end:
Triaged: N issues
ready-for-agent: N ← entry point for /supergraph:plan
needs-info: N
ready-for-human: N
wontfix: N
ready-for-agent unless acceptance criteria are unambiguousready-for-human for anything requiring architecture, security, or business decisionsneeds-info issues — don't dump all questions at oncewontfix always requires a reason in the commentNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
The English summary is being prepared. Showing the original description.
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
The English summary is being prepared. Showing the original description.
Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
The English summary is being prepared. Showing the original description.
Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.
The English summary is being prepared. Showing the original description.
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
The English summary is being prepared. Showing the original description.
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
The English summary is being prepared. Showing the original description.