SZ

smalltechorg/zero-shot-harness

Database management

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

0 stars 품질 49 트렌드 8

zero-shot spec-driven-development harness for building agents spec-first

개요

Three skills for building software . Give it a one-line idea; walk away with a working, tested, phased project — on whatever stack the requirements pick. The skills are : install them once and they operate on whatever project repo you point them at. — the spec derives the stack, designs the layout, and a scaffold gate proves the skeleton runs before any feature work. The skills are disable-model-invocation: true — trigger them explicitly: 1. Written before code; when they disagree, the spec wins (/sync). 2. Your stated preferences are binding; everything else is derived from the requirements and recorded with rationale. The scaffold gate proves the skeleton runs before any feature work. 3. Each phase ships the smallest increment a human can test, and it must work the first time. 4. Autonomous within a phase; stops at each boundary for you to test the increment. 5. Every spec includes spec/agent.md — the idea evaluated against the agentic-patterns catalogue.

README

원문 README의 일부입니다. 원문 보기.

Zero-Shot Harness — spec-first, AI-native project building

Three skills for building software spec-first. Give it a one-line idea; walk away with a working, tested, phased project — on whatever stack the requirements pick. The skills are repo-independent: install them once and they operate on whatever project repo you point them at. No default stack, no boilerplate to clone — the spec derives the stack, designs the layout, and a scaffold gate proves the skeleton runs before any feature work.

The three skills

Skill Purpose
build Idea → working, verified, phased project. Also adds a capability to an existing project.
fix Diagnose + fix a bug / error / failing test / drift, then verify.
sync Reconcile spec ↔ code (spec wins), then verify.

The skills are disable-model-invocation: true — trigger them explicitly:

/build 
/fix 
/sync [scope]

The Spirit

  1. Spec is the source of truth. Written before code; when they disagree, the spec wins (/sync).
  2. No default stack. Your stated preferences are binding; everything else is derived from the requirements and recorded with rationale. The scaffold gate proves the skeleton runs before any feature work.
  3. Smallest first-time-right win, phase by phase. Each phase ships the smallest increment a human can test, and it must work the first time.
  4. A human gates every phase. Autonomous within a phase; stops at each boundary for you to test the increment.
  5. AI-native by design. Every spec includes spec/agent.md — the idea evaluated against the agentic-patterns catalogue. “No AI capability needed” is a legitimate written conclusion; an unexamined design is not.
  6. Real services or it doesn’t count. Gates run against the real external services the spec names — the real LLM when the design has AI capability, the production database engine always. A stubbed pass is not a pass.

Install

The skills/ tree follows the open Agent Skills standard, so it runs on Claude Code (as a plugin), Hermes (as skills), and any other Agent-Skills-compatible tool. The support/ tree is the shared doctrine; only the thin platform wrappers differ.

Claude Code

/plugin marketplace add smallTechOrg/zero-shot-harness
/plugin install zero-shot-harness@zero-shot-harness

The three skills, four sub-agents, and the shared support/ material all come with the plugin. Confirm with /plugin (it should list zero-shot-harness as enabled). Then do the one-time Claude Code autonomy setup for each project you build in — without it, every build command raises a permission prompt and the “autonomous within a phase” promise breaks.

To uninstall:

/plugin uninstall zero-shot-harness --scope project
/plugin marketplace remove smallTechOrg/zero-shot-harness
GitHub에서 전체 README 보기

추천 도구

다른 키워드를 입력하거나 필터를 제거해 보세요.

설치

npx skillfish add smalltechorg/zero-shot-harness
MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →