workbench-algorithm-advisory-gate
Workbench Algorithm Advisory Gate
Use this skill when an issue declares SDD_STAGE: Algorithm Advisory Gate,
asks for algorithm review before Task List, or assigns the Remote Algorithm
Advisor.
Required Source Reads
- The latest
SDD_STAGE: Technical Designblock. docs/algorithm-advisory-gate-lane.md.- The scoped files named by
code_scopeorSCOPED_EVIDENCE. - The mounted
data-algoskill entrypoint.
Do not read unrelated issue history or broad repo trees unless the Technical Design names that evidence.
Runtime Boundary
- Advisory-only. Do not edit repo files.
- Do not mutate global Claude Code settings,
.capy/settings.json, Multica runtime config, Sanity datasets, credentials, or Workbench Max. - Use per-lease temporary
HOMEand temporary Claude config when running in a VM or disposable cell. - If the exact GPT-5.5 xhigh model setup is unavailable, return
FLAGwith the observed model readback.
Required Report
ALGO_ADVISORY_REPORT
target_issue:
source_stage: Technical Design
runtime:
model:
isolation:
skill_sources:
code_scope:
correctness_verdict: PASS | BLOCK
complexity_verdict: PASS | FLAG | BLOCK
data_structure_notes:
algorithmic_risks:
task_list_injections:
verification_injections:
settings_readback:
residual_risk:
VERDICT: PASS | FLAG | BLOCK
Verdicts
PASS: no correctness blocker and complexity risk is acceptable.FLAG: Task List may proceed only if advisory injections become explicit tasks, checks, or residual risks.BLOCK: Technical Design must be revised before Task List because the advisor found a concrete correctness, data-loss, privacy, concurrency, or semantic risk.
More from fearvox/multica-ultimate-workbench
workbench-conductor
Two-ring orchestration, routing, issue and comment discipline, and role boundaries for the Multica Workbench.
5workbench-sdd
Specification-driven development from raw requirement to product design, technical design, task list, execution, and verification.
5workbench-self-awareness-infra
Capability discovery and current-state verification for Heavy Path, ambiguous repo/runtime ownership, and runtime-dependent Standard Path work.
5workbench-design-docs
Product design, technical design documents, user-facing copy, specs, diagrams, and handoff documentation.
5workbench-token-context-discipline
Compact context, cache-aware execution, scoped evidence reads, and role-specific skill attachment discipline.
4workbench-product-brainstorming
Bounded product ideation, workflow design, ambition checks, tradeoffs, and smallest-test shaping.
4