architect
Sketches types, signatures and module structure before code is written, then stays in the loop during implementation.
- Kind
- Skill
- Works with
- Cursor, Any agent
- Source
- cursor/plugins @ 9580c23696ac
- Path
- pstack/skills/architect/SKILL.md
- License
- MIT
- Jobs
- Planning
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Architect Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. ## Start Open a todolist with one entry per phase before starting. 1. Ground 2. Sketch 3. Agree 4. Implement 5. Scrap ## Phase A: Ground the problem Build a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Naming a file isn't grounding. Produce the architectural explanation `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess. Skip Phase A only when the work is genuinely greenfield with no surrounding system to integrate. ## Phase B: Sketch Run the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references/runner-prompt.md` as each runner's prompt. …