spec-driven-development/spec-as-source
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
PLAN.mdskills/plan-mode/templates/
goal: > What this project is trying to reach. One paragraph. This changes rarely — only when the scope genuinely changes. done-when: > How anyone can tell the goal has been reached. Observable conditions, not intentions. plan-version: 1
PLAN —
Il piano è la sorgente della sequenza dei change, come la spec è la sorgente del codice. Nessun
openspec-proposesenza una voce qui, approvata. Gate meccanico:bash scripts/check-plan-gate.sh.
Entries
.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-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