CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

SKILL.mdskills/plan-judge/prompts/round-2/

name:
plan-judge-round-2
description:
Behavior contract for the fixed four-pass Round 2 development-document workflow.

Plan Judge Round 2

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.

README.md

tile.json