Craft work-unit tracker records with observable outcomes and acceptance criteria.
npx skills add https://github.com/tesserine/groundwork --skill work-unit-craft
Please help me install this Agent Skill. Skill: work-unit-craft Source: https://github.com/tesserine/groundwork/tree/main/skills/work-unit-craft Command: npx skills add https://github.com/tesserine/groundwork --skill work-unit-craft
A work-unit's tracker record transfers problem understanding across a context boundary — from the author who sees the problem to the agent who will solve it. The implementing agent has no access to the author's context, codebase familiarity, or unstated assumptions. Everything it needs must be in the record. Forges name the record differently — GitHub says issue, SourceHut says ticket — the craft is the same on every forge.
Create a new work-unit record capturing the problem, acceptance criteria, and the contract inputs for downstream implementers.
High-intent search queries and answers about installing and using this skill.
A work-unit tracker record transfers problem understanding across context boundaries from author to agent. It captures observable outcomes, constraints, and governance decisions so downstream implementers can act without hidden context or unstated assumptions.
To write a work-unit record, state observable outcomes, recipient documentation contracts, and governance decisions. Anchor the record with reckoned constraints and author contract inputs to preserve the problem statement throughout the decompose and pivot phases.
Yes, the work-unit documentation craft works across forge environments. GitHub names the record an issue, SourceHut calls it a ticket, but the craft of transferring problem context and anchoring constraints remains the same on every forge platform.
Work-unit acceptance criteria should include observable outcomes, reckoned constraints, and author contract inputs. Including governance decisions and aligning with the contract lifecycle ensures downstream implementers have everything needed without accessing the author's original context.
Update work-unit records during decompose, pivot, and record review phases across planning, execution, and verification. This ensures the work-unit lifecycle remains aligned with the original problem and the contract lifecycle throughout context delegation.
No, contract inputs and governance decisions are essential. Without anchoring the record with these elements, future implementers lose the recipient documentation contract and cannot act accurately without hidden context from the original problem author.
samuel-morrisseyGenerate a Product Requirements Document from conversation context and publish it to the issue tracker.
shaul1991Enforce PLAN, REVIEW, EXECUTE, and RE-VERIFY governance across project lifecycle phases.
troykellyCreate or validate GitHub issues with acceptance criteria and project board links.
spqwProvides DOM event, timer, and MQTT generators for Blazor hybrid apps.
