start-work

Orchestrate task work through gated phases from claim to handoff.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cjennings/rulesets --skill start-work-cjennings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-work
Source: https://github.com/cjennings/rulesets/tree/main/start-work
Command: npx skills add https://github.com/cjennings/rulesets --skill start-work-cjennings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pick up a task and guide it through a disciplined, gate-driven workflow from Claim to Hand-off, ensuring clear ownership, rationale, and verification before progress.

Core Features & Use Cases

  • Gate-driven phases: Phase 0 eligibility, Phase 1 claim, Phase 2 justify (gate 1), Phase 3 approach (gate 2), Phase 4 implement (TDD), Phase 5 verify, Phase 6 ready-to-commit (gate 3), Phase 7 hand off to the Review-and-Publish flow.
  • Structured decision points: Each phase requires explicit approvals and documentation to reduce ambiguity and rework.
  • Multi-reference workflow: Works with Linear tickets, GitHub issues, todo.org tasks, or free-form scopes; supports optional scripts/references/assets as described in SKILL.md.

Quick Start

Run /start-work <task-ref> to begin the guided multi-phase workflow for the chosen task.

Frequently Asked Questions about start-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a gated workflow with task ownership from kickoff to handoff?

A gated workflow enforces task ownership by guiding tickets through defined phases like Claim, Justify, Approach, Implement, Verify, and Hand-off, requiring explicit approvals and documentation before progressing to reduce ambiguity and rework.

Can I use this gated workflow process with Linear tickets and GitHub issues?

Yes, the gated workflow process works with Linear tickets, GitHub issues, todo.org tasks, or scoped descriptions. It orchestrates task work across these multi-reference formats to ensure clear ownership through each phase.

What is the best way to start a task using a TDD-based gated workflow?

The best way to start a TDD-based gated workflow is to run the start-work command with your task reference. This initiates a guided multi-phase workflow, walking the task through eligibility, claim, justification, approach, and TDD implementation.

How does phase gating reduce ambiguity in software project management?

Phase gating reduces ambiguity by inserting structured decision points between phases. Each gate requires explicit approvals and documentation, ensuring the rationale, approach, and verification of the task are validated before moving forward.

Does the task management workflow support TDD-based implementation and verification?

Yes, the task management workflow explicitly includes a TDD-based implementation phase followed by a verify phase. This ensures the implementation meets requirements before reaching the ready-to-commit gate and final hand-off.

When should I not use a multi-gate workflow for task management?

A multi-gate workflow adds structured decision points and documentation overhead, so it may not suit simple or trivial tasks. It is designed for scoped descriptions and complex work requiring strict ownership, rationale, and verification.