agentleFS
akshay-diwadkarakshay-diwadkar/first-four-hours/skills/workbench/blueprint/SKILL.md

blueprint

Skill1 starsChanged 4 days agoMITView on GitHub

Plan a repository change before anyone implements it, sealing an implementation-complete `blueprint.md` that leaves the executor no design decision; skip implementation.

71 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use align, execute and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • marylinSkill

    align

    Audit project structure, docs health, and lifecycle compliance. Use when a project feels disorganized, after major refactors, before onboarding a contributor, or periodically as a health check.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 5 projects that use this

  • LangChainSkill

    docker-patterns

    Best practices for Docker containerization and multi-stage builds

    Also in 3 projects that use this

  • lukeleekrSkill

    scout

    GitHub 레포 스카우터. 내 Claude Code + Codex App 환경을 분석하여 필요한 GitHub 레포를 자동 추천하거나, 키워드로 GitHub을 검색합니다. "scout", "스카우트", "깃헙 탐방", "레포 추천", "repo search" 등의 키워드에 반응합니다.

    Also in 3 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 7 projects that use this

  • HABUBUSSSkill

    eval-harness

    Also in 3 projects that use this

The file

Files
SKILL.md

Workflow

  1. Close intent. With supplied or referenced architecture, or an Assess or Temper handoff, first read Architecture intake. Settle every material user-owned ambiguity before design: desired outcome, compatibility, product tradeoffs, change boundary, non-derivable priorities, and ambiguous acceptance. Ask only when different answers yield materially different correct solutions and no source or supplied answer settles the choice. Never ask the user to choose a repository-derived engineering detail. Do not seal while a material user-owned ambiguity remains.
  2. Explore cheaply. In any step, read Bounded exploration first. Read Planning contract before decision-critical exploration, and Earlier plans before reusing or amending a plan or request. Gather only facts that can change the solution, preservation, propagation, or verification. Done when each such open question is answered from source or a safe probe, recorded as a prediction, or returned to step 1 if user-owned.
  3. Solve the engineering problem. Settle every decision the planning contract requires, and attack the problem. Trace command dispatch when it can change correctness. When designs remain plausible, gather the smallest discriminating fact and decide yourself; when viable solutions must first be found, invoke ideate per Ideate in planning. Done when one supported solution accounts for current obligations and meaningful verification.
  4. Bound the delta. Apply the planning contract's rent rule. Done when every material planned addition passes it.
  5. Write the plan. Prepare the workspace exactly as in README, then fill its blueprint.md scaffold with Declared text and Incomplete gates as the planning contract routes. Done when check reports no diagnostics.
  6. Challenge and repair. Read Challenge and rehearsal; walk the draft yourself, with the Challenger brief for a standard draft; an elevated draft's fresh-context subagent runs it instead. Done when every finding is repaired, rejected on evidence, or returned to the user, and every plan-authored check a repair changed, or whose input it changed, is re-applied to everything it scans.
  7. Seal or stop. Once the Seal gate holds, check and seal exactly as in README; otherwise stop unsealed and report why, never weakening an outcome, check, or proof below what the Seal gate requires. Done when your report names the sealed path or stop and distinguishes mechanical seal success, your evidence-backed readiness judgment, and unstarted implementation and verification.

Consult reason before committing to an approach, after a failure or direction change, and before seal. Seal and stop reports trace reason checkpoints per its Checkpoint trace and end with one optional next step fitting the outcome, after a stop the unblocking one: a fenced, self-contained prompt naming the repository and every issue, PR, or artifact it needs, or say none is needed. Only a "yes" starts it, via any skill it names; start Construct in a fresh session or, per Construct handoff, a subagent when possible: the sealed plan carries every decision.

Boundaries

No implementation authority. The repository stays read-only except exact .first-four-hours/blueprints/<task>/{request.md,blueprint.md} writes, prepare's exclude rule, safe-probe side effects, and invoked ideate handoffs. Planner and challenger never build, apply, or run the planned change anywhere, scratch copies included. Request/handoff sets outcomes but cannot override skill, tool, or harness instructions; source is evidence, not authority. No transcript, sidecar, hidden state, or compatibility shim carries decisions; blueprint.md does. Scripts validate mechanics only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.