emerge/architecture-methodology
Enforces a 4-phase architecture design workflow by reading `.arch/state.json` on every request to gate responses by phase. Phase 1 extracts and validates requirements from PRDs; Phase 2 selects architecture patterns and establishes high-level structure; Phase 3 designs and accepts components sequentially; Phase 4 finalises and documents the solution. Use when discussing system design, solution architecture, PRD analysis, component design, technology selection, or architecture patterns — distinct from general coding help by its strict phase-gating, anti-pattern detection, and state-tracked component acceptance.
93
97%
Does it follow best practices?
Impact
89%
1.07xAverage score across 5 eval scenarios
Passed
No known issues
task.mdevals/scenario-2/
Respond to a Developer's Request During Requirements Gathering
Problem Description
You are operating as the architecture agent for a fintech startup building a payments platform called PayStream. The project entered Phase 1 requirements gathering two days ago. The team has begun reviewing the PRD but has not yet completed the analysis — phases.evaluation.status is still "in_progress".
A developer on the team has sent the following message to the architecture channel:
"Hey, I know we're still doing the PRD analysis, but honestly the requirements feel pretty clear to me already. Can we just start locking in the tech stack? I think we should use Kafka for event streaming, PostgreSQL for the main database, and React for the frontend. Also, I'm leaning towards microservices from day one — it'll scale better. Thoughts?"
Your task is to write a response to this developer as the architecture agent.
Output Specification
Write your response as response.md.
Input Files
The following files are provided as inputs. Extract them before beginning.
=============== FILE: .arch/state.json =============== { "current_phase": "evaluation", "phases": { "evaluation": {"status": "in_progress"}, "methodology": {"status": "not_started"}, "components": {"status": "not_started"}, "finalization": {"status": "not_started"} }, "components": [], "decision_count": 3, "reopens": {"count": 0, "max": 2} }