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-1/

name:
plan-judge-round-1
description:
Behavior contract for the fixed four-turn Round 1 plan rewrite and review loop.

Plan Judge Round 1

Round 1 contains exactly four turns. In every turn the writer rewrites the entire plan and the judge reviews that rewrite. The providers exchange roles on every turn, but the role prompt files do not change.

Use the shared rubric for both roles:

  1. cosa non va
  2. cos'e' migliorabile
  3. e' fattibile
  4. di cosa ho bisogno
  5. che tecnologie servono

There is no convergence decision, quality threshold or early exit inside Round

  1. The runner owns sequencing and digest validation. The fourth writer output is the Round 1 Markdown result, after which control returns to the human.

skills

README.md

tile.json