Architect

A skill named in bold or in backticks, or run as /<name>, is the file ../<name>/SKILL.md beside this skill's directory, and a principle named without its prefix is ../principle-<name>/SKILL.md. Read the file and follow it. Most pstack skills are user-only, so your skill tool cannot load them.

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 task list (your harness's task tool, or a checklist file at ~/.local/state/pstack/checklists/<repo>-<branch>.md when it has none) with one entry per phase before starting.

Ground
Sketch
Agree
Implement
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.