CtrlK
BlogDocsLog inGet started
Tessl Logo

matthew-a-carr/draft-spec

Draft a SPEC from a GitHub issue and open a PR for review. Use when triggered by a routine on `Issue opened` with label `ai:plan`, or when a user asks to "draft a spec from issue #NNN". Non-interactive — proceeds on best interpretation and surfaces any unresolved questions in the SPEC's §Open Questions section rather than blocking for clarification. The PR review loop is where ambiguity gets resolved.

78

3.03x
Quality

90%

Does it follow best practices?

Impact

100%

3.03x

Average score across 1 eval scenario

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Evaluation results

100%

67%

Feature Spec PR Submission

Spec PR submission workflow

Criteria
Without context
With context

No gh CLI

0%

100%

ai:planned before PR

41%

100%

Commit message format

0%

100%

PR title format

12%

100%

PR body includes Open Questions

0%

100%

PR body includes review-spec verdict

0%

100%

PR body links to source issue

100%

100%

ai:revise label on PR

0%

100%

Issue comment wording

10%

100%

Spec index updated

100%

100%

No implementation

100%

100%

git push uses CLI

100%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents