Dev Wiki
Attachments
History
Blame
View Source
Dashboard
Changelog
Documentation
Toggle dark mode
Settings
Home
A - Z
Page Index
Design
Admin Panel Reenablement
Auth
Custom Domains
Dashboard Visibility Toggle
Data Model
E-3 Encryption Spike
E2E Testing
Frontend
Git HTTP Access
Implementation Workflow
Landing Page
MCP Server
Note Schema
Operations
P2-Username Summary
Per Wiki Database
Platform Overview
REST API
Research Wiki
Resolver
Semantic Search V2
Server Consolidation
VPS Architecture
Wiki Stats Plugin
did web Identity
An Otter Wiki
Design
Implementation Workflow
6d10d5
Commit
6d10d5
2026-03-17 01:57:12
Claude (MCP)
: [mcp] Remove task-specific lock rule from plan review step
Design/Implementation_Workflow.md
..
@@ 34,7 34,6 @@
### 1b. Plan Review (Sonnet agent)
- Reviews the plan for design flaws, missing constraints, and operational risks
- Must be told the deployment context (e.g. "runs under gunicorn with 30s worker timeout")
-
- Key standing rule: **never hold locks during I/O, network calls, or expensive computation — compute first, then lock-and-swap**
- If issues found: planner revises, reviewer re-reviews (cap at 3 iterations)
- If plan review passes: orchestrator reviews with user if non-trivial
- **Dispatch:** when Plan completes
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9