constructive-harness

Installation
SKILL.md

constructive-harness — the harness build workflow

You're in a project driven by the Constructive harness: the host registers typed database tools and tracks build progress in .constructive/feature_list.json. This umbrella skill routes the whole workflow; read only the reference that matches the current state.

Which reference to read

Current state Read
.constructive/ missing in the project references/init.md — lay down the harness skeleton, hand back
.constructive/BRIEF.md still the template stub references/brief-intake.md — collect the brief, write BRIEF.md + per-entity feature rows
Deciding what to do next in a build references/build-orchestrator.md — the feature_list.json state machine: pick the next feature, verify, mark status
Before any database/schema/codegen action, or choosing which tool fits a purpose references/tools.md — the typed tools, harness rule IDs, and the script-docs → tools bridge

Typical flow: init → brief intake → orchestrator loop (each iteration: pick feature → tools reference for backend steps → verify → record).

Ground rules (apply across all references)

Installs
2
First Seen
9 days ago
constructive-harness — constructive-io/constructive-skills