Skip to main content
This is the starter path we are aiming to ship for beta. It is built for TypeScript teams that want the smallest useful workflow.
Beta note: this page describes the target starter flow. Some commands and tooling are still in progress.

​
Start with one loop

Do only three things:
  1. write one small spec
  2. build from it
  3. verify it in CI
That is enough to start.

​
Step 1: Write one small spec

Start with one important thing:
  • one API route
  • one module
  • one service
  • one workflow
Put one file in specs/. Example: 
specs/
  user-login.spec.md
Keep it small. The file should say:
  • what this thing is
  • what must stay true
  • one or two examples
  • what should prove it

​
Step 2: Build from the spec

Use the spec as the contract for the work. A human writes the intent. A human and an AI update:
  • code
  • tests
  • docs
The simple rule is: do not add behavior that is not in the spec.

​
Step 3: Verify it

Run one check locally. For beta, the goal is a flow like this: 
spec check
Then run the same check in CI. That is what keeps the loop alive for the whole team.

​
What the beta starter should feel like

We want the starter experience to feel like: 
spec init
spec check
And in GitHub Actions: 
- uses: specleddev/spec-check-action@v0
That is the target.

​
What to skip at first

Do not start with:
  • heavy traceability
  • proposals
  • ADRs
  • conformance matrices
  • pre-commit hooks
Those can come later. For the starter path, CI is the main shared guard.

​
What success looks like

A TypeScript developer should be able to:
  • read one page
  • write one spec file
  • build one feature from it
  • run one check
  • let CI enforce the same check
If it feels harder than that, the starter flow is still too complex.