CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-ai/spec-as-source

Adds spec-as-source enforcement to any project using spec-driven development

87

2.34x
Quality

91%

Does it follow best practices?

Impact

82%

2.34x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-4/

Use spec-as-source-setup to add spec-as-source enforcement to this project.

Project state:

  • tessl init has already been run
  • tessl-labs/spec-driven-development is already installed
  • The git repo is initialized (git init done)
  • No scripts/ directory exists yet
  • No .pre-commit-config.yaml exists
  • No .github/workflows/ directory exists
  • The project uses pytest

After creating all files, ask the user which test runner to use before finalising the CI workflow, show the post-setup checklist, then run spec-verify.

README.md

tile.json