Plan

Use when an approved, clarified spec must become a technical blueprint before any code — the SDD phase between clarify and tasks: architecture, contracts, data flow, testing strategy, sequencing and risks, at structure altitude, never framework syntax. NOT the what/why spec (that is `specify`), NOT the ambiguity sweep (that is `clarify`), NOT the task breakdown (that is `tasks`), NOT the code (that is `implement`).

ericrisco Updated 610 repo stars
rsc-harness: you build the product, rsc-harness builds your agent's harness, following strict best practices instead of improvising one.

File contents

ericrisco/rsc-harness commit 87e452035c

Frequently asked questions

npx get-skill add ericrisco/plan