workbench-sdd
Workbench SDD
Use this skill when a task needs to move from a fuzzy request into executable work.
This is the default workbench planning protocol unless the issue explicitly says the task is a quick fix, emergency repair, or direct verification run.
Pipeline
Move work through these stages:
- Raw Requirement
- Capture the user's literal request.
- Separate confirmed facts from assumptions.
- Name the owner, expected output, and known constraints.
- Product Design
- Define the user-facing behavior, success criteria, non-goals, and edge cases.
- Keep the scope narrow unless the user asks for expansion.
- Technical Design
- Identify the runtime owner, data path, files, commands, integrations, and risk surface.
More from fearvox/multica-ultimate-workbench
workbench-token-context-discipline
Compact context, cache-aware execution, scoped evidence reads, and role-specific skill attachment discipline.
7workbench-memory-synthesis
Durable memory, session summaries, decision logs, issue closeout synthesis, and compact handoffs.
7workbench-research
Evidence-first research, architecture discovery, vendor documentation review, benchmark reading, and unknown-system analysis.
7workbench-conductor
Two-ring orchestration, routing, issue and comment discipline, and role boundaries for the Multica Workbench.
7workbench-review-qa
PASS, FLAG, and BLOCK review discipline for workflow review, QA verification, release checks, and issue closeout.
7workbench-design-docs
Product design, technical design documents, user-facing copy, specs, diagrams, and handoff documentation.
7