Skip to content

Latest commit

 

History

History

shape-work

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

README.md

Shape Work

Clarify an idea in project terms: goals, users, scope, priorities, constraints, trade-offs and success. Start at SKILL.md for standalone discovery or a bounded caller handoff. It asks focused follow-ups across relevant workflows, exceptions and trade-offs, retains required/deferred/excluded/accepted-limitation dispositions, and visibly tracks what remains. Each round asks the next questions, names a blocker, or presents a brief for confirmation. It explicitly says “Shaping complete” only after the agreement is usable and confirmed; document updates alone do not end discovery.

A confirmed plan completes shaping without a spec, ticket or storage artifact. The user chooses the next stage; the agent may offer it without starting it. Project work reuses meaningful existing guidance and reports specific missing responsibilities rather than requiring a setup template.

Current decisions and supported research/analysis are reused. Readily available reliable facts are inspected directly; technical gaps go to compatible Analyze or Research, not questions asking you to design internal abstractions or test seams. Analysis that could change behavior, feasibility, compatibility, scope or consequential trade-offs happens before brief confirmation, directly in the caller's context without a separate /analyze command. Implementation-only analysis may remain a later phase when it cannot change the agreement. Missing goals, expectations and other owner-held context are asked directly rather than inferred from search. For work spanning people/items, readiness covers each in-scope item, not just shared guidance; deferring required context needs owner agreement. Actual meaning or decision-record changes use Domain Modeling with its own approval gates.

Installation and dependencies

After approving the exact installation scope:

npx skills add SirDarcanos/agentskills --skill shape-work

This example has not been executed. Copy the complete package and its MIT notice. Plain discovery needs authorized source inspection and a conversation channel. Conditional companions are discovered through runtime/project catalogs or approved locations, not sibling directories. Read their complete entries and relevant references and check behavior, not names alone. Missing material sources or required companions block dependent decisions; they do not trigger installation or legacy grilling.

Discovery grants no implementation, ticket publication, model, delegation or external-effect permission. Optional delegated work needs separate authority and a compatible conditional Work On coordination library; an old universal-contract-only package blocks delegation, not direct shaping. In standalone use the return ends at the discovery brief. Work On uses this companion for unresolved product intent and discovered Write Spec for specification writing/publication. Stage those packages coherently; settled actionable agreements need no fresh shaping run. Merging source does not change installed copies or retire grilling.

Validation and provenance

Read validation for package checks and conversation/reuse cases. Static checks and direct synthetic walkthroughs are not installed-runtime or autonomous agent certification.

Extracted from repository-owned Work On discovery with original project-oriented instructions. The shipped Nicola Mustone MIT notice covers reused material; no external instruction body or template is newly imported.