deepwork-brainstorming

Clarifies goals, constraints, and risks before implementation through proportional discovery and design.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/hugefiver/ocmm --skill deepwork-brainstorming-hugefiver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepwork-brainstorming
Source: https://github.com/hugefiver/ocmm/tree/main/plugins/deepwork/skills/deepwork-brainstorming
Command: npx skills add https://github.com/hugefiver/ocmm --skill deepwork-brainstorming-hugefiver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous or creative work often starts without a shared understanding of the goal, constraints, and acceptance criteria, leading to rework, scope drift, and misaligned implementations. This Skill structures discovery and design so material uncertainty is resolved before code is written, without imposing rigid ceremony on clear tasks. ## Core Features & Use Cases - Proportional Discovery Paths: Chooses between direct/bounded, spike, and architectural investigation based on actual uncertainty and risk rather than fixed checklists. - Authorization and Escalation Rules: Distinguishes authorized scope from decisions requiring user consent, such as API changes, destructive actions, or expanded permissions. - Outcome-Oriented Design: Produces design artifacts scaled to the work, covering goals, interfaces, risks, and wave-based acceptance evidence. - Use Case: Before implementing a new feature touching multiple services, use this Skill to explore approaches, record bounded rulings, and hand off a clear goal with acceptance criteria to the implementation workflow. ## Quick Start Ask the agent to brainstorm and clarify the design for your planned feature before writing any code.

Frequently Asked Questions about deepwork-brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify requirements before implementing a feature with an AI agent?▼

Invoke the brainstorming workflow before implementation to identify the goal, constraints, acceptance criteria, and risks. The Skill scales discovery to actual uncertainty, so clear tasks proceed directly while ambiguous ones get structured exploration.

When should I use a design document versus proceeding directly to code?▼

Proceed directly when the goal, affected flow, and acceptance criteria are materially clear. Create a durable design artifact when boundaries, interfaces, dependencies, or consequential trade-offs remain unresolved and coordination justifies the documentation.

Does this brainstorming workflow require user approval at every step?▼

No. Approval is requested only when a decision changes scope, weakens security or data guarantees, alters public APIs, or triggers irreversible actions. A clear imperative request is treated as authorization to implement that stated scope.

Can this Skill work with Codex instead of OpenCode?▼

Yes. The Skill includes a Codex compatibility section mapping OpenCode constructs like TodoWrite and task dispatch to Codex equivalents such as update_plan and the current callable dispatch schema, preserving the workflow contract.

What are the limitations of a lightweight discovery process?▼

Lightweight discovery is unsuitable when concrete security, data-loss, compatibility, protocol, migration, or irreversible-operation risks exist. Those conditions require heavier investigation and explicit escalation rather than bounded rulings.