work-shaping
Skill0 starsChanged 4 months agoMITView on GitHub
Decide how much process a task deserves before coding: tiny vs substantial, chat vs GitHub, checklist vs execution brief, architecture lane vs full bundle, operator review vs council, and private diary vs public draft. Use when the shape of the work is the blocker.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Luoah7/WPSTask-skillstheir own version, first seen Sep 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Luoah7/WPSTask-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- continuity-ledgerSkill
- github-mobile-opsSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- openclaw-councilSkill
- parallel-worktreesSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- session-to-postSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- visual-explainerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not use when: the next step is already clearly implementation and no shaping decision remains.
- Distinctive: line 22
No ceremony for tiny reversible work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Work Shaping
Metadata
- Trigger when: the user is not blocked by code yet, but by uncertainty about how much process, tracking, or review the work deserves.
- Do not use when: the next step is already clearly implementation and no shaping decision remains.
Skill Purpose
Choose the smallest honest operating lane for a task so small work stays light and meaningful work gets durable structure before it disappears into chat.
Instructions
- Classify the work across the main axes: size, durable surface, planning depth, architecture lane, review lane, and artifact/public-writing lane.
- Choose the smallest honest process that matches those axes. If architecture is not
none, route toward$spec-bundle; if durable tracking is needed, route toward GitHub or another explicit source of truth; if the user already implied action, do not stop at classification. - Return a compact shaping verdict that names the recommended next lane immediately instead of leaving the process choice implied. If another skill is needed, list only the valid next skill options in the form
$skill-name— one-line purpose.
Non-Negotiable Acceptance Criteria
- No ceremony for tiny reversible work.
- Substantial work does not vanish into chat without a durable surface.
- Architecture risk is made explicit instead of buried inside vague planning language.
- The answer distinguishes what is already real from what is only the recommended next step.
Output
- A compact shaping verdict across the main axes.
- The recommended next lane or skill.
- The one or two main reasons that process level is justified.
Next skill options(only if needed):$idea-validation— validate buyer/pain/wedge truth;$spec-bundle— create implementation-ready contracts and gates;$justdoit— create plan/status/test-plan for execution;$product-council— pressure-test a fuzzy high-impact choice.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.