From geas
Pre-implementation agreement — worker proposes concrete action plan, quality_specialist and design_authority approve before implementation begins. Prevents wasted implementation cycles from misunderstood requirements.
npx claudepluginhub choam2426/geasThis skill uses the workspace's default tool permissions.
Worker and reviewers agree on "what done looks like" before any code is written.
Generates implementation plans from completed designs with file paths, code examples, tests, verification steps for engineers lacking codebase context.
Executes implementation plans by dispatching builder agents per task with spec compliance and code quality reviews. Use for independent tasks or triggers like 'build this' or 'execute the plan'.
Executes implementation plans from tasks.md files with plan review, batch task processing, verifications, and code review checkpoints.
Share bugs, ideas, or general feedback.
Worker and reviewers agree on "what done looks like" before any code is written.
Orchestrator invokes this skill after Design Guide (design_authority) and before Implementation, for every task.
Eliminates the waste cycle: "worker misunderstands requirement → builds wrong thing → quality verification catches it → rework." The worker reads the ContextPacket (including communication_specialist's design and design_authority's design guide), then explicitly states what they plan to do and how they'll prove it's done. quality_specialist and design_authority approve before implementation begins.
.geas/missions/{mission_id}/tasks/{task-id}.json.geas/missions/{mission_id}/packets/{task-id}/{worker}.mdSpawn the assigned worker to read their ContextPacket and write a contract:
Agent(agent: "{worker}", prompt: "Read .geas/missions/{mission_id}/packets/{task-id}/{worker}.md and .geas/missions/{mission_id}/tasks/{task-id}.json. Before implementing, write your implementation contract to .geas/missions/{mission_id}/contracts/{task-id}.json with these fields:
- planned_actions: concrete steps you will take
- edge_cases: edge cases you plan to handle
- state_transitions: state changes your implementation introduces (if any)
- non_goals: what you explicitly will NOT do
- demo_steps: step-by-step procedure to verify your work is complete
Set status to 'draft'.")
Verify .geas/missions/{mission_id}/contracts/{task-id}.json exists.
Spawn quality_specialist to review the contract from a quality verification perspective:
Agent(agent: "quality-specialist", prompt: "Read .geas/missions/{mission_id}/contracts/{task-id}.json and .geas/missions/{mission_id}/tasks/{task-id}.json. Review this implementation contract:
- Are demo_steps sufficient to verify all acceptance criteria?
- Are there missing edge_cases that should be handled?
- Are non_goals reasonable — anything critical being excluded?
- Would you be able to test this based on what's described?
Write your assessment. If acceptable, approve. If not, list specific concerns.")
Spawn design_authority to review the contract from a technical perspective:
Agent(agent: "design-authority", prompt: "Read .geas/missions/{mission_id}/contracts/{task-id}.json, .geas/missions/{mission_id}/tasks/{task-id}.json, and any prior design guide at .geas/missions/{mission_id}/evidence/{task-id}/design-authority.json. Review this implementation contract:
- Are planned_actions consistent with the design guide?
- Are non_goals appropriate — nothing critical being excluded?
- Are there technical edge_cases the worker missed?
- Is the approach viable or heading toward a dead end?
Write your assessment. If acceptable, approve. If not, list specific concerns.")
"approved", set approved_by. Proceed to Implementation.Write the contract to .geas/missions/{mission_id}/contracts/{task-id}.json conforming to schemas/implementation-contract.schema.json.
mkdir -p .geas/missions/{mission_id}/contracts
Log the event:
Append to .geas/ledger/events.jsonl:
{"event": "implementation_contract", "task_id": "...", "status": "approved|revision_requested", "timestamp": "..."}