start-task-work

Validate docs/tasks/*.md task documents and produce an implementation plan.

8|1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/dianlight/srat --skill start-task-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-task-work
Source: https://github.com/dianlight/srat/tree/main/.github/skills/start-task-work
Command: npx skills add https://github.com/dianlight/srat --skill start-task-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting complex work from predefined task documents with safety checks and traceability, ensuring a linked GitHub issue and proper planning before coding.

Core Features & Use Cases

  • Enforces guardrails: creates or links GitHub issues for tasks, branches from main when needed, and generates a pre-implementation plan.
  • Supports strict-id mode to require numeric task IDs.
  • Applies to teams that manage work from docs/tasks and want consistent kickoff processes.

Quick Start

Issue a start-task-work instruction to pick a docs/tasks/**.md file, validate the task, and produce a ready-to-implement plan.

Frequently Asked Questions about start-task-work

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

FAQPage Schema
How do I create a GitHub issue from a task document before coding?

To create a GitHub issue from a task document, the skill validates your markdown task file and automatically creates or links an issue in the dianlight/srat repository, ensuring traceability before development begins.

What is strict-id mode for task management workflows?

Strict-id mode is a task management workflow configuration that enforces numeric task IDs and requires exact target resolution when identifying and validating markdown task documents.

How do I generate a pre-implementation plan for development work?

To generate a pre-implementation plan, the skill validates your markdown task document, ensures branch safety by branching from main, and produces an approved handoff plan before any coding starts.

Does this task kickoff process enforce branch safety from main?

Yes, the task kickoff process enforces branch safety by branching from main when needed, validating the markdown task document, and updating it after each phase before handing off the implementation plan.

Why do I need to link a GitHub issue before starting development work?

Linking a GitHub issue before starting development work provides strict guardrails and traceability, ensuring your predefined markdown task documents have a validated plan and connected issue before any coding begins.