Menu
Explore possibilities for a topic by combining research digests with project knowledge and governance context.
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.
Basé sur la classification professionnelle SOC
| name | brainstorm |
| description | Explore possibilities for a topic by combining research digests with project knowledge and governance context. |
/brainstorm <topic>
Creative exploration tool. Reads research digests, project knowledge, and governance docs to explore possibilities for a given topic. Output stays in the conversation unless the user asks to save it.
Lifecycle position: Before review-issue — exploratory thinking before
an issue exists. Can also be used mid-task to explore alternatives.
Read available knowledge sources:
.agent/knowledge/research_digest.md — workspace research (if exists).agent/project_knowledge/research_digest.md — project research (symlink to manifest repo's .agents/workspace-context/; may not exist).agent/project_knowledge/ — aggregated project knowledge (symlink to .agents/workspace-context/; may not exist)docs/PRINCIPLES.md — workspace principles (for feasibility checks)AGENTS.md — workspace-wide agent rules and conventionsARCHITECTURE.md — system design and layering constraintsdocs/decisions/ — ADRs for historical contextPRINCIPLES.md, .agents/README.md,
ARCHITECTURE.md, docs/decisions/) when the topic is project-specificCheck digest freshness — if older than 30 days, note it and suggest
running /research --refresh but don't block on it.
For the given topic, consider:
Structure the output as:
## Brainstorm: <topic>
### Current State
<what exists today>
### Possibilities
1. **<approach>** — <description>
- Pros: ...
- Cons: ...
- Research: <reference to digest entry if applicable>
2. **<approach>** — ...
### Gaps
- <what's missing that any approach would need>
### Principle Considerations
- <any principle alignment issues>
### Suggested Next Steps
- <concrete actions to explore further or begin implementation>
Host orchestrator that drives an issue through the full per-issue lifecycle — dispatches each phase (review-issue → plan-task → review-plan → implement → review-code → triage-reviews → address-findings) as a fresh-context sub-agent, reads each phase's progress.md entry to choose the next action, and pauses at user checkpoints. Local-first: the PR is created at the end, never auto-pushes or auto-merges without confirmation.
Evaluate a GitHub issue against workspace principles and ADRs before work begins. Records findings in progress.md and best-effort posts them as a comment on the issue.
Independent evaluation of a committed work plan before implementation begins. Checks scope, approach, principle alignment, consequences, and ROS conventions.
Activate deployment mode for a live field deployment. Discovers the project's deployment config, detects dev/field side via field_mode.sh, and either creates a new deployment, first-activates an existing one (worktree/main-tree + per-host log + issue-sync push), or resumes an ongoing one. Loads the urgency contract (sterile-cockpit / mitigate-before-diagnose / time-box) into the current agent session.
Close out a field deployment. Verifies dev-side access, finds the open deployment issue, collects field logs, interviews the operator for corrections, consolidates the dev log, reconciles field code via SHA-preserving merge and /import-field-changes, opens the wrap-up PR (Closes
Lead reviewer that orchestrates specialist sub-reviews (static analysis, governance, plan drift, adversarial) to evaluate a PR or pre-push diff. Scales review depth to change risk. Produces a unified structured report and persists findings to progress.md.