pstack-architect
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pstack-architect
- description
- Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
02 资源文件 4
- 许可证LICENSE1.0 KB
- 参考文档references/design-red-flags.md2.9 KB
- 参考文档references/rationale-template.md3.0 KB
- 参考文档references/runner-prompt.md3.3 KB
03 SKILL.md 正文
Architect
Sketch types, function signatures, class shapes, and module boundaries with not implemented bodies and pseudocode. Compare independent design alternatives, then fill in code against the chosen sketch.
Start
Open a todolist 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 guide 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 guide 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 guide with the design-sketch task and the Phase A grounding artifacts. Pass references/runner-prompt.md as each runner's prompt.
Use existing FirstMate delegates or the current harness's delegation tools with their configured model and effort. Without delegation, compare designs in separate passes.
Design it twice. Require at least two structurally distinct candidates before synthesis, even when the first looks sufficient. This is the exhaust-the-design-space guide made concrete. Whole-shape alternatives, not point fixes inside one shape.
Screen every candidate against references/design-red-flags.md before synthesis. Assume the next contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Prefer the design where a change that looks right from one file is right for the whole repo.
Compare viable candidates on interface depth. Prefer the design that hides more complexity behind a smaller, simpler public surface. A rich interface can keep call chains short by concentrating capability instead of scattering it across layers.
Arena returns one synthesized design package. Its synthesis decision fills the rationale's "Synthesis decision" section.
Phase C: Agree (opt-in)
Default: proceed directly to implementation with the synthesized design. No human checkpoint.
Opt in to a checkpoint when the invoker explicitly asks: "/architect with checkpoint," "stop and show me before implementing," or similar. Then surface the synthesized design and pause for sign-off.
The synthesis can ship as its own commit either way, as the "scaffold first" mode of the foundational-thinking guide. Planned and scoped breakage during fill-in is fine, per the outcome-oriented-execution guide. For adversarial pressure on the design before implementing, run the interrogate guide on the synthesized sketch.
If the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.
Phase D: Implement against the sketch
Replace not implemented bodies with code, pseudocode with logic. The synthesized sketch is the contract. Deviations from it are signal to surface, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching.
Phase E: Scrap when the architecture is wrong
If implementation keeps producing friction the sketch can't absorb, throw the sketch out. Don't bolt fixes onto a wrong design, per the redesign-from-first-principles and fix-root-causes guides.
The signal is a pattern, not single instances. Tells:
- The same shape of workaround appearing repeatedly across unrelated code.
- Multiple unrelated edge cases that all need special-case branches.
- Types that need escape hatches (
any, casts, optional fields always set in practice) to compile. - The "we need a lock" reflex when the sketch said the state wasn't shared.
- Callers having to know the abstraction's internal rules to use it.
- Two or more independent Phase D deviations of the same shape across the implementation.
Use judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex. Complexity in the data is not complexity in the design.
When you scrap:
- Re-run the how guide over what's been built.
- Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.
- Subtract before adding, per the subtract-before-you-add guide. The new sketch should be smaller than the old one before it grows.
- Return to Phase B and re-run arena.
Outputs
The caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes. Module map plus type definitions for larger work. The rationale ships alongside, shaped per references/rationale-template.md, including the usage sketch and the synthesis decision.
04 同仓库更多 Skills
teach
Teach the user a new skill or concept, within this workspace.
stop-overthinking
Manually-invoked skill that stops overthinking and forces a short, practical decision. Use only when the user explicitly invokes stop-overthinking.
remind
Rewrite the last response simpler and shorter in plain English, prefixed with a 3-5 sentence TLDR of the conversation so far. Manual-only, invoked as /remind.
read-all-adrs
Read every ADR markdown file in the project's docs/adr/ folder so you have full context on past decisions. Use only when the user explicitly calls it.
pstack-why
Find evidence for design choices and historical constraints through relevant authorized read-only sources; distinguish facts, inferences, and gaps.
pstack-unslop
Cut AI tells from any writing.