skills.rest
avelikiy
avelikiyCOMMUNITY
Explore all skills by this author →
GitHub

done-blocked

Report terminal work statuses as 'DONE' or 'BLOCKED' with evidence.

75|13|Updated Apr 5, 2026
Search Tags:#task management#status tracking#project communication#work status reporting#workoutcomes
One-click install
npx skills add https://github.com/avelikiy/great_cto --skill done-blocked
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: done-blocked
Source: https://github.com/avelikiy/great_cto/tree/main/skills/done-blocked
Command: npx skills add https://github.com/avelikiy/great_cto --skill done-blocked

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill helps in streamlining and standardizing the reporting of work statuses, ensuring that terminal outcomes are reported clearly and unambiguously.

Core Features & Use Cases

  • Standardizes Status Reporting: Enforces a specific format for marking tasks as either 'DONE' or 'BLOCKED' with required information.
  • Enhances Communication: Facilitates clear communication about work status by requiring concrete and actionable feedback.
  • Use Case: After completing a code review, the Skill requires a developer to report the status as 'DONE' or 'BLOCKED', detailing any issues if necessary.

Quick Start

Upon completing a task, use the skill to report its status by executing the command and providing the required details.

Frequently Asked Questions about done-blocked

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

FAQPage Schema
How do I standardize work status reporting in a development pipeline?▼

Standardize work status reporting by enforcing terminal outcomes as 'DONE' or 'BLOCKED' with concrete evidence. This ensures clear, unambiguous communication about task completion or failure within work pipelines.

What is the best way to report blocked tasks with actionable feedback?▼

Report blocked tasks by marking the status as 'BLOCKED' and detailing the specific issues encountered. This enforces actionable feedback and prevents vague communication about work pipeline failures.

How does terminal status tracking work for code review outcomes?▼

Terminal status tracking for code reviews works by requiring developers to report a final 'DONE' or 'BLOCKED' status, detailing any issues found to ensure clear and specific work outcome communication.

Can I use this status reporting skill without additional dependencies?▼

Yes, you can use this status reporting skill without additional dependencies. It operates via scripts to enforce specific work status formats, requiring no external libraries or environment setup.

Why does my work pipeline need standardized task completion statuses?▼

Your work pipeline needs standardized task completion statuses to eliminate ambiguity. Enforcing 'DONE' or 'BLOCKED' formats with evidence streamlines project communication and prevents misaligned work outcomes.

Related Skills

Explore More Software Engineering Skills→
79yuuki79yuuki

verification-before-completion

Require fresh verification evidence before reporting work as complete.

Community
Intermediate
hackefellerhackefeller
1

jinn-check

Generate structured status reports with Done, In Progress, Blocked, Next, Risks, and Recommendation sections.

Official
Intermediate
pwnk77pwnk77
59

Progress Tracker

Track task completion and generate automated project status reports.

Community
Intermediate
ngochuy13ngochuy13

task-tracker

Tracks project tasks lifecycle from creation to completion with enforced workflows and overdue escalation.

Community
Intermediate