skills/delegated-delivery/SKILL.md
Run a meaningful coding ticket through a delegated delivery workflow: tighten the ticket, assign one ticket owner, delegate implementation, get an independent review, scan for high-value simplification, validate the result, and return a compact outcome packet. Use when the user wants structured agent execution with clear scope, ownership, and review rather than a single-pass implementation. Triggers on: "delegate this ticket", "use a sub-PM", "run this through worker and reviewer", "own this ticket end to end", "send this for independent review", or "close this ticket out with review". Skip trivial fixes and tasks that are still too vague to delegate.
npx skillsauth add rarestg/rarestg-skills delegated-deliveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use a layered execution model:
references/SOP.md is the canonical operating model. Read it when you are
actually running a ticket through this workflow.
Use this workflow only when the user clearly wants delegated or agent-based delivery, a worker/reviewer loop, independent review, or ticket ownership. Do not infer delegation from a generic request to finish or close out work.
Dispatch prompts should be free-form, not forced into templates. Preserve the ticket contract in whatever shape fits the work: problem, invariants, scope, non-goals, source-of-truth order, acceptance criteria, validation, and escalation triggers.
When spawning subagents, pass ticket-local context plus the directly relevant sources of truth. Do not preload unrelated tickets or broad program context.
tools
Break large code changes into small, stacked pull requests using vanilla git and the gh CLI. Auto-trigger when implementing a feature or change that spans multiple logical steps, touches several files, or will exceed ~200 changed lines. Also trigger on "stack PRs", "break this into smaller PRs", "stacked diffs", or "create a PR stack". Do NOT trigger for single-file fixes, small bug fixes, or changes under ~200 lines that are a single logical unit.
development
Export a PR's clean inline review comments, CodeRabbit outside-diff comments, and CodeRabbit nitpicks into local files, then triage review feedback through a stack-aware orchestrator workflow with durable reply drafts for follow-up PRs. Use when given a GitHub pull request URL and asked to work through review comments without relying on noisy raw API blobs.
development
Run reusable Graphify-led architecture analysis for codebases using semantic graphs, optional subagent extraction, graph synthesis, source-search validation, graph-shape review, and follow-up refactor planning. Use when asked to analyze repo architecture, god nodes, surprising edges, topology, module boundaries, or graph-derived cleanup/refactor opportunities.
data-ai
Operating protocol that uses Taskwarrior as the continuity layer across conversations. Grounds every interaction in real task state before acting. Activate on "morning" / "briefing" for daily overview, on "status" / "what's next" for current state, when capturing tasks ("remind me to", "add task", "I need to"), when recovering from stalls, or when executing structured work across projects, repos, and life domains.