name: loom-architecture
description: "Architectural Mapping: Use this to produce technical design documents from approved requirements."
triggers:
patterns: ["(architecture|design|structure|data model)", "how should I (build|structure|implement)"]
goals: ["system-design", "architectural-analysis"]

Loom Feature Architect

Turn requirements into a technical specification.

Input

• request (required): The user's original literal request or a concise orchestrator-synthesized restatement. Anchors the architectural work to user intent when no brainstorming summary is present.
• brainstorming_summary (optional): Loom Summary from the brainstorming subagent — present on the full pipeline route; absent on the short "architecture first" route

Core Rules

1. Analyze Input: Read the brainstorming output or PRD.
2. Map System: Define components, data models, and API interfaces.
3. Bottlenecks: Explicitly identify potential security or performance issues.
4. Principles: High cohesion, low coupling, and TDD-ready design.

Output

Produce a Loom Summary block at the end of your work:

## Loom Summary
- status: complete | partial | blocked
- output: <one-line description of what was produced>
- artifact: <file path or "none">
- decisions: <key choices made, 1-3 bullets>
- blockers: <what's preventing progress, or "none">
- suggested_next: loom-plan-writing

(Canonical definition: PROTOCOL.md)