work
/work
Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
- Author
- TechDufus ↗
- Repository
- dotfiles ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
Original author description
Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
How it works
- First Pass
- Mode
- Noise Filter
- Closeout
SKILL.md preview
--- name: work description: Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams. metadata: short-description: Route complex work --- # Work Route complex work into the smallest execution shape that preserves evidence, focus, and momentum. Do not duplicate narrower skills; let debugging, TDD, review, PR, or platform-specific skills own their lanes. ## First Pass - Outcome: name the concrete deliverable. - Scope: identify files, systems, and non-goals. - Evidence: find the source of truth before editing. - Risk: decide what can break and how to check it. ## Mode - `quick`: one obvious local step. Execute directly. - `research`: user needs location, explanation, or confidence. Inspect source and answer. - `structured`: dependent steps or multi-file edits. Use `update_plan`, then work sequentially. - `parallel`: independent units with disjoint write scopes. Delegate only sidecar tasks when permitted; keep the blocking path local. - `orchestrated`: large, staged work. Decompose into waves; wait only when blocked. - `unclear`: ambiguity risks the outcome. Ask the smallest question. ## Noise Filter - No plan for a one-step fix. - No broad repo tour before the owning file or API is checked. - No delegation for trivial or blocking work. - No unrelated cleanup, refactor, or commentary. - No completion claim without evidence. ## Closeout Report what changed, what verified it, and any remaining risk or unverified edge.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · TechDufus/dotfiles | 90 | Apache-2.0 |
| arxdsilva/ai-loops | 100 | MIT |
| minanyang/10x-agent | 100 | MIT |
| cwinvestments/memstack | 100 | MIT |
| Khouini/trunks-spec | 100 | MIT |
| x-cmd/x-cmd | 100 | Apache-2.0 |
| HubSpot/agent-cli-skills | 100 | Apache-2.0 |
| OutlineDriven/outline-driven-development | 100 | Apache-2.0 |
| mtrense/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version b39731d3eaf2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100software-engineering
For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work,… - 100context-retrieval-loop
Use when about to write a new doc, README section, or ADR, updating existing documentation with unclear scope, or spawning a documentation subagent that needs file context.