Menu
Have a business-goal discussion using the context base without drafting the deliverable.
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
Run the full autonomous pipeline against a work item — plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a GitHub issue
The Notion bridge for work items — creates a Notion work item mirroring a GitHub issue, uploads artifacts (item.md, refs/, plan.md, wrapup.md) to it, and pulls a work item's artifacts down to ./tmp/<id>/. Used by /create-feature, /create-epic, /create-issue (publish) and /do (pull before work, upload after). Use when a work item needs to be published to, updated in, or fetched from Notion.
Create Excalidraw diagram JSON files and PR visual overviews that make visual arguments. Use when the user wants to visualize workflows, architectures, concepts, pull request changes, before/after behavior, or a shareable explainer image for reviewers.
Dispatches one Codex (GPT-5.6) sub-agent via `codex exec` — implementer, backend-verifier, plan-reviewer, code-reviewer, code-researcher, or investigator — and returns its report. Used by /do, /discussion, and /create-issue whenever one of these roles runs; not normally invoked by the user directly. Use when a pipeline stage needs its Codex sub-agent dispatched, resumed for a fix round, or re-run.
Captures a discussed multi-phase workstream as an Epic Spec work item ready for /do. For a single-outcome change use /create-feature instead.
Captures a discussed feature as a lean Feature Ticket work item ready for /do. For multi-phase workstreams use /create-epic instead.
| name | business-discussion |
| description | Have a business-goal discussion using the context base without drafting the deliverable. |
Role: Main human-in-the-loop stage. Before discussing, you MUST make sure the context base exists. NEVER discuss on empty context.
Rules:
.business/context/ is missing or empty, you MUST run or request business-context; for serious work you MUST also run or request business-research-adversary. The discussion MUST be grounded in real internal + external context, never guesses.Read:
.business/context/context.md.business/context/research-adversary.md.business/context/known-facts.md.business/context/assumptions-unknowns.md.business/context/constraints.mdWrite:
.business/discussion/brief.mdOutput: