task-status

Parse task documents and generate a Markdown report grouped by status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reads all task documents in docs/tasks and generates a grouped progress report, suitable for weekly standups, GitHub comments, or PR descriptions.

Core Features & Use Cases

  • Reads all task files in docs/tasks/ matching NNn_*.md (excluding README.md) and extracts TaskID, Type, Title, Status, Issue Links, and Progress.
  • Groups tasks by status (๐Ÿ“… Planned / ๐Ÿ”„ In Progress / โœ… Done) and renders a Markdown report suitable for sharing with teams.
  • Supports optional filters by Type (FEATURE/FIX/DOCS/REFACTOR) or by linked repo to narrow down the scope.

Quick Start

To generate the latest report, run the skill against your docs/tasks directory and paste the resulting Markdown into your standup note.

Frequently Asked Questions about task-status

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

FAQPage Schema
How do I generate a task progress report from markdown files for a daily standup?โ–ผ

To generate a task progress report, you read markdown files in your tasks directory to extract TaskID, Type, Status, and Progress, then assemble a grouped markdown report suitable for standups or GitHub comments.

What is the best way to aggregate task statuses from multiple markdown documents?โ–ผ

Aggregating task statuses involves parsing each markdown file to derive metadata like Status and Issue Links from headers, then grouping the collected tasks by status into a unified markdown report.

Can I filter my task report by task type or linked GitHub repository?โ–ผ

Yes, you can filter the generated task report by specific task types like FEATURE or FIX, or by linked repository, allowing you to narrow down the scope of the aggregated progress output.

How do markdown task files need to be structured for automated status extraction?โ–ผ

Markdown task files should use leading digits for TaskID, a heading for Type, text after the prefix for Title, and a Status header, allowing the parser to extract metadata and infer missing statuses automatically.

Does the task status report include details for in-progress tasks?โ–ผ

Yes, the task status report includes a Next: hint for in-progress tasks when applicable, alongside the extracted Issue Links and Progress counts, providing clear context for ongoing work.