Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub deandum/claude-resources --plugin go-skillsHow this command is triggered — by the user, by Claude, or both
Slash command
/claude-resources:definecommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
**Required first action.** Invoke the Skill tool with `core/orchestration` NOW, before any other step. Do NOT spawn any subagent, derive any slug, or write any file until the skill is loaded and Step 1 (directory + template copy + preflight) has been executed. Skipping this step was the root cause of a past run where subagents wrote `discovery.md` into `.claude/` instead of `docs/specs/<slug>/`. You — the main Claude — are the lead. Do NOT spawn a `lead` subagent. Run Phase 1 (Analysis — spawn critic + scout in parallel, Gate 1 findings review, optional Gate 1 clarification round-trip) an...
/defineClarifies and scopes project problems using multi-AI consensus from Claude, Gemini, and Codex providers, producing synthesized technical requirements and next-step options.
/defineCaptures requirements from brainstorming docs, meeting notes, or direct input, validates clarity via scoring, and produces a structured requirements specification file.
/defineGuides the user through defining a problem statement using the Working Backwards methodology, saving output to a markdown file.
Share bugs, ideas, or general feedback.
Required first action. Invoke the Skill tool with core/orchestration NOW, before any other step. Do NOT spawn any subagent, derive any slug, or write any file until the skill is loaded and Step 1 (directory + template copy + preflight) has been executed. Skipping this step was the root cause of a past run where subagents wrote discovery.md into .claude/ instead of docs/specs/<slug>/.
You — the main Claude — are the lead. Do NOT spawn a lead subagent.
Run Phase 1 (Analysis — spawn critic + scout in parallel, Gate 1 findings review, optional Gate 1 clarification round-trip) and Phase 2 (Spec Generation — synthesize spec.md, Gate 2 approval). Stop after Gate 2 with spec.md frontmatter at status: approved.
Do NOT enter Phase 3. Execution is a separate user-invoked step (/orchestrate --resume <slug> or /build).
Task: $ARGUMENTS
If the task is too vague for a spec, suggest /ideate first.