summarise

Analyze project markdown files to summarize development task status.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill summarise-marcuskrogh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarise
Source: https://github.com/marcuskrogh/skills/tree/main/skills/summarise
Command: npx skills add https://github.com/marcuskrogh/skills --skill summarise-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the ambiguity of project status by providing a clear, consolidated view of where a specific task or story stands within your development workflow.

Core Features & Use Cases

  • Contextual Status Reporting: Aggregates data from roadmap, plan, and issue tracking files to provide a comprehensive summary of a task.
  • Workflow Stage Detection: Automatically identifies the current stage of a task, such as setup, implementation, review, or ship-ready, based on existing documentation.
  • Use Case: When you are unsure of the current progress on a feature or bug fix, use this skill to get an immediate summary of the task's status, artifacts, and the recommended next step.

Quick Start

Ask the agent to summarise the current issue by typing the command followed by the issue key.

Frequently Asked Questions about summarise

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

FAQPage Schema
How do I generate a status summary for my development pipeline?

To generate a status summary, the system analyzes project-specific markdown files like ROADMAP, PLAN, and ISSUES to synthesize task progress across feature, bug, and iteration pipelines. It identifies current workflow stages and suggests logical next steps.

What's the best way to track workflow state across features and bug fixes?

Tracking workflow state is best handled by aggregating roadmap, plan, and issue tracking data to detect the current stage of a task. This approach eliminates ambiguity by providing a consolidated view of whether a task is in setup, implementation, review, or ship-ready.

Do I need specific markdown files to get a project status report?

Yes, you need project-specific markdown files including ROADMAP, PLAN, and ISSUES to get an accurate status report. The system requires these files to synthesize task summaries and recommend next steps.

How does workflow stage detection work for development tasks?

Workflow stage detection works by automatically identifying the current stage of a task, such as setup, implementation, review, or ship-ready, based on existing project documentation and workflow state files.

When do I need a consolidated view of my development task progress?

You need a consolidated view of development task progress when you are unsure of the current status of a feature or bug fix. It provides an immediate summary of the task's status, artifacts, and recommended next steps.

Can I summarise an issue without manually reviewing all documentation?

Yes, you can summarise an issue without manual review by providing the issue key. The system automatically aggregates data from roadmap, plan, and issue tracking files to deliver the summary.