mcpField
C
construct

construct

github.com/akshay-diwadkarDevelopment173 installsUpdated today
Repository

About construct

construct is a skill for implementing and verifying code changes against a sealed Blueprint. It guides development work through ordered steps, command-based checks, and a final comparison of the diff with the plan.

Key features

  1. 01Implement Blueprint steps in order
  2. 02Apply declared blocks through commands
  3. 03Run proof and verification flows
  4. 04Preserve unrelated worktree changes
  5. 05Report diffs and verification results

Use cases

  1. 01Implement a feature from a Blueprint
  2. 02Resume an interrupted execution
  3. 03Check implementation against the plan

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/akshay-diwadkar/first-four-hours --skill construct

After installing, type/constructin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

skill-protocol.json
agents/
openai.yaml
references/
delegation-protocol.md
execution-contract.md
failure-and-resume.md
safety-and-recovery.md
scripts/
_diagnostic_contract.py
_skill_protocol_runtime.py
blueprint_runtime.py
cli.py
run_verification.py

Details

From the project README

Construct

Authority

Construct persists no execution state and creates no execution artifact. Blueprint owns every planning decision; Git worktree state owns the implementation delta. Discovery is evidence, not authority: it cannot expand a sealed Blueprint. The Blueprint stays byte-for-byte unchanged. Preserve unrelated dirty work; execution requires a Git worktree. Scripts prove mechanics only; the agent owns attribution, scope truth, and completion.

Command

python <construct>/scripts/cli.py --repo-root <repo> --input blueprint_file=<blueprint.md> --input phase=before --format json verify

Judge criteria first; follow next_command when present, else required_action.

Smooth execution loop

  1. Intake. Read Execution contract once, then run verify before for fresh work, status for resume. For dirty targets, non-Git paths, concurrent, destructive, or recovery work read Safety. Read the whole Blueprint before editing; when a caller quotes or paraphrases it, reread that step and work from its sealed text.
  2. Implement each ### N. in order. apply writes declared blocks, never by hand: with Red:, apply Frozen, write prose tests, prove its declared red, then apply Exact. Implement the rest, then prove green with the caller-held next unused attempt and follow its forward guidance. Repair only what Blueprint settles; otherwise stop as plan-contradiction.
  3. Verify. Run verify phase after; judge every Expect:. Execute Runs only through verify or reverify, on resume too. Repair locally only when Blueprint fixes the answer, then reverify from the earliest invalidated Run line. A shown declared Incomplete: outcome ends as verification-incomplete after step 4. Else stop with plan-contradiction evidence. Timeout or mutation failures are unsafe, never reverify.
  4. Reconcile and report. Compare the final diff against the sealed Blueprint once, per the Execution contract. Consequential behavior or safety risk, meaningful propagation, indirect verification, or a hard-to-observe acceptance condition earns an Earned Conformance Review; else none. Report instructions, each Proof run and Run with its Expect: and quoted output showing whether it met it, unrecoverable red gaps, notices, any caller quote the Blueprint lacks, whether a review was earned, run, or earned and not run, and whether protected paths and HEAD are unchanged.

Exceptions

Stopping ends the Construct run: plan-contradiction, protected-work-conflict, or safety-contradiction, reported with exact evidence. Failure, resume, and stopping owns failing Runs, resume, and what happens next.

Final and stop reports end with one optional next step fitting this outcome, after a stop its recovery owner's: a fenced, self-contained prompt naming any repository, issue, PR, or artifact it needs, or say none is needed. Only a "yes" starts it, via any skill it names, but the user runs a charter, diagnose, or ticket step as its /<skill> command.

Comments

Markdown supported