Spec-driven development on OpenSpec, with mechanical spec-as-source enforcement: a custom 'spec-as-source' OpenSpec schema adds file-ownership (targets) and test-verification ([@test]) metadata to every capability spec, three scripts (link check, ownership check, manifest build) keep code and specs from drifting apart, plus requirement-gathering, spec-writer, work-review, and a session-handoff skill with a proactive context-warning hook.
68
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Round 2 has exactly four sequential passes in a fixed role order: research,
fact verification, development-document writing and goal review. Two of those
roles produce (research, writing) and two of them check (verification, goal
review). The two providers are assigned so that each of them produces once and
checks once — the producing roles never fall to the same provider, and neither
do the checking roles. Each pass reads one named on-disk artifact and writes one
new artifact under .plan-judge/round-2/.
The final document names every technical choice, its source, its reason and its goal-relative advantage. Do not approve plans, calculate hashes, write plan state fields or start another round.
.tessl-plugin
rules
skills
handoff
handoff-skill
openspec-apply-change
openspec-archive-change
openspec-explore
openspec-propose
openspec-sync-specs
plan-judge
plan-mode
prompt-engineer
prompt-loop
requirement-gathering
spec-as-source-setup
templates
openspec-schema
spec-as-source
templates
spec-ci-sync
spec-loop
spec-rebuild
spec-verify
spec-writer
work-review