Skip to main content
issue-discover Unified issue discovery and creation. Create issues from GitHub/text, discover issues via multi-perspective analysis, or prompt-driven iterative exploration. Triggers on "issue:new", "issue:discover", "issue:discover-by-prompt", "create issue", "discover issues", "find issues".
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/catlog22/Claude-Code-Workflow --skill issue-discoverLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Plus depuis ce dépôt CCW command help system. Search, browse, recommend commands, skills, teams. Triggers "ccw-help", "ccw-issue".
Lightweight execution engine - multi-mode input, task grouping, batch execution, chain to workflow-lite-test-review
Lightweight planning skill - task analysis, multi-angle exploration, clarification, adaptive planning, confirmation, and execution handoff
Explorateur de fichiers
5 fichiers Métiers associés SOC
Basé sur la classification professionnelle SOC
name issue-discover description Unified issue discovery and creation. Create issues from GitHub/text, discover issues via multi-perspective analysis, or prompt-driven iterative exploration. Triggers on "issue:new", "issue:discover", "issue:discover-by-prompt", "create issue", "discover issues", "find issues". allowed-tools spawn_agent, wait_agent, send_message, followup_task, close_agent, request_user_input, Read, Write, Edit, Bash, Glob, Grep, mcp__ace-tool__search_context, mcp__exa__search
Issue Discover
Unified issue discovery and creation skill covering three entry points: manual issue creation, perspective-based discovery, and prompt-driven exploration.
Architecture Overview
┌─────────────────────────────────────────────────────────────────┐
│ Issue Discover Orchestrator (SKILL.md) │
│ → Action selection → Route to phase → Execute → Summary │
└───────────────┬─────────────────────────────────────────────────┘
│
├─ request_user_input: Select action
│
┌───────────┼───────────┬───────────┐
↓ ↓ ↓ │
┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ Phase 1 │ │ Phase 2 │ │ Phase 3 │ │
│ Create │ │Discover │ │Discover │ │
│ New │ │ Multi │ │by Prompt│ │
└─────────┘ └─────────┘ └─────────┘ │
↓ ↓ ↓ │
Issue Discoveries Discoveries │
(registered) (export) (export) │
│ │ │ │
│ ├───────────┤ │
│ ↓ │
│ ┌───────────┐ │
│ │ Phase 4 │ │
│ │Quick Plan │ │
│ │& Execute │ │
│ └─────┬─────┘ │
│ ↓ │
│ .task/*.json │
│ ↓ │
│ Direct Execution │
│ │ │
└───────────┴──────────────────────┘
↓ (fallback/remaining)
issue-resolve (plan/queue)
↓
/issue:execute
Key Design Principles
Action-Driven Routing : request_user_input selects action, then load single phaseProgressive Phase Loading : Only read the selected phase documentCLI-First Data Access : All issue CRUD via ccw issue CLI commandsAuto Mode Support : -y flag skips action selection with auto-detectionSubagent Lifecycle : Explicit lifecycle management with spawn_agent → wait_agent → close_agentRole Path Loading : Subagent roles loaded via path reference in MANDATORY FIRST STEPS
Auto Mode When --yes or -y: Skip action selection, auto-detect action from input type.
Usage issue-discover <input>
issue-discover [FLAGS] "<input>"
# Flags
-y, --yes Skip all confirmations (auto mode)
--action <type> Pre-select action: new|discover|discover-by-prompt
# Phase-specific flags
--priority <1-5> Issue priority (new mode)
--perspectives <list> Comma-separated perspectives (discover mode)
--external Enable Exa research (discover mode)
--scope <pattern> File scope (discover/discover-by-prompt mode)
--depth <level> standard|deep (discover-by-prompt mode)
--max-iterations <n> Max exploration iterations (discover-by-prompt mode)
# Examples
issue-discover https://github.com/org/repo/issues/42 # Create from GitHub
issue-discover "Login fails with special chars" # Create from text
issue-discover --action discover src/auth/** # Multi-perspective discovery
issue-discover --action discover src/api/** --perspectives=security,bug # Focused discovery
issue-discover --action discover-by-prompt "Check API contracts" # Prompt-driven discovery
issue-discover -y "auth broken" # Auto mode create
Execution Flow Input Parsing:
└─ Parse flags (--action, -y, --perspectives, etc.) and positional args
Action Selection:
├─ --action flag provided → Route directly
├─ Auto-detect from input:
│ ├─ GitHub URL or #number → Create New (Phase 1)
│ ├─ Path pattern (src/**, *.ts) → Discover (Phase 2)
│ ├─ Short text (< 80 chars) → Create New (Phase 1)
│ └─ Long descriptive text (≥ 80 chars) → Discover by Prompt (Phase 3)
└─ Otherwise → request_user_input to select action
└─ Initialize progress tracking: functions.update_plan([...phases])
Phase Execution (load one phase):
├─ Phase 1: Create New → phases/01-issue-new.md
├─ Phase 2: Discover → phases/02-discover.md
└─ Phase 3: Discover by Prompt → phases/03-discover-by-prompt.md
Post-Phase:
└─ Summary + Next steps recommendation
Phase Reference Documents
Core Rules
Action Selection First : Always determine action before loading any phaseSingle Phase Load : Only read the selected phase document, never load all phasesCLI Data Access : Use ccw issue CLI for all issue operations, NEVER read files directlyContent Preservation : Each phase contains complete execution logic from original commandsAuto-Detect Input : Smart input parsing reduces need for explicit --action flag⚠️ CRITICAL: DO NOT STOP : Continuous multi-phase workflow. After completing each phase, immediately proceed to nextProgressive Phase Loading : Read phase docs ONLY when that phase is about to executeExplicit Lifecycle : Always close_agent after wait_agent completes to free resources
Input Processing
Auto-Detection Logic function detectAction (input, flags ) {
if (flags.action ) return flags.action ;
const trimmed = input.trim ();
if (trimmed.match (/github\.com\/[\w-]+\/[\w-]+\/issues\/\d+/ ) || trimmed.match (/^#\d+$/ )) {
return 'new' ;
}
if (trimmed.match (/\*\*/ ) || trimmed.match (/^src\// ) || flags.perspectives ) {
return 'discover' ;
}
if (trimmed.length > 0 && trimmed.length < 80 && !trimmed.includes ('--' )) {
return 'new' ;
}
if (trimmed.length >= 80 ) {
return 'discover-by-prompt' ;
}
return null ;
}
Action Selection (request_user_input)
const answer = functions.request_user_input ({
questions : [{
header : "Action" ,
id : "action" ,
question : "What would you like to do?" ,
options : [
{
label : "Create New Issue (Recommended)" ,
description : "Create issue from GitHub URL, text description, or structured input"
},
{
label : "Discover Issues" ,
description : "Multi-perspective discovery: bug, security, test, quality, performance, etc."
},
{
label : "Discover by Prompt" ,
description : "Describe what to find — Gemini plans the exploration strategy iteratively"
}
]
}]
});
const actionMap = {
"Create New Issue (Recommended)" : "new" ,
"Discover Issues" : "discover" ,
"Discover by Prompt" : "discover-by-prompt"
};
functions.update_plan ([
{ id : "action-select" , title : "Action Selection" , status : "completed" },
{ id : "phase-exec" , title : `Phase: ${selectedAction} ` , status : "in_progress" },
{ id : "post-phase" , title : "Post-Phase: Next Steps" , status : "pending" }
])
Data Flow User Input (URL / text / path pattern / descriptive prompt)
↓
[Parse Flags + Auto-Detect Action]
↓
[Action Selection] ← request_user_input (if needed)
↓
[Read Selected Phase Document]
↓
[Execute Phase Logic]
↓
[Summary + Next Steps]
├─ After Create → Suggest issue-resolve (plan solution)
└─ After Discover → Suggest export to issues, then issue-resolve
Subagent API Reference
spawn_agent Create a new subagent with task assignment.
const agentId = spawn_agent ({
agent_type : "{agent_type}" ,
message : `
## TASK ASSIGNMENT
### MANDATORY FIRST STEPS (Agent Execute)
1. Execute: ccw spec load --category exploration
2. Execute: ccw spec load --category debug (known issues cross-reference)
## TASK CONTEXT
${taskContext}
## DELIVERABLES
${deliverables}
`
})
wait_agent Get results from subagent (only way to retrieve results).
const result = wait_agent ({
timeout_ms : 1800000
})
if (result.timed_out ) {
}
if (result.status [agentId].completed ) {
const output = result.status [agentId].completed ;
}
followup_task Assign new work to active subagent (for clarification or follow-up).
followup_task ({
target : agentId,
message : `
## CLARIFICATION ANSWERS
${answers}
## NEXT STEP
Continue with plan generation.
`
})
close_agent Clean up subagent resources (irreversible).
close_agent ({ target : agentId })
Core Guidelines Data Access Principle : Issues files can grow very large. To avoid context overflow:
Operation Correct Incorrect List issues (brief) ccw issue list --status pending --briefRead('issues.jsonl')Read issue details ccw issue status <id> --jsonRead('issues.jsonl')Create issue echo '...' | ccw issue createDirect file write Update status ccw issue update <id> --status ...Direct file edit
ALWAYS use CLI commands for CRUD operations. NEVER read entire issues.jsonl directly.
Error Handling Error Resolution No action detected Show request_user_input with all 3 options Invalid action type Show available actions, re-prompt Phase execution fails Report error, suggest manual intervention No files matched (discover) Check target pattern, verify path exists Gemini planning failed (discover-by-prompt) Retry with qwen fallback Agent lifecycle errors Ensure close_agent in error paths to prevent resource leaks
Post-Phase Next Steps Progress : functions.update_plan([{id: "phase-exec", status: "completed"}, {id: "post-phase", status: "in_progress"}])
After successful phase execution, recommend next action:
functions.request_user_input ({
questions : [{
header : "Next Step" ,
id : "next_after_create" ,
question : "Issue created. What next?" ,
options : [
{ label : "Plan Solution (Recommended)" , description : "Generate solution via issue-resolve" },
{ label : "Create Another" , description : "Create more issues" },
{ label : "Done" , description : "Exit workflow" }
]
}]
});
functions.request_user_input ({
questions : [{
header : "Next Step" ,
id : "next_after_discover" ,
question : `Discovery complete: ${findings.length} findings, ${executableFindings.length} executable. What next?` ,
options : [
{ label : "Quick Plan & Execute (Recommended)" , description : `Fix ${executableFindings.length} high-confidence findings directly` },
{ label : "Export to Issues" , description : "Convert discoveries to issues" },
{ label : "Done" , description : "Exit workflow" }
]
}]
});
functions.update_plan ([{ id : "post-phase" , status : "completed" }])
Related Skills & Commands
issue-resolve - Plan solutions, convert artifacts, form queues, from brainstormissue-manage - Interactive issue CRUD operations/issue:execute - Execute queue with DAG-based parallel orchestrationccw issue list - List all issuesccw issue status <id> - View issue details 