completion-status

Standardize multi-step workflow completion statuses with predefined labels and escalation format.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/jedrecord/hal2026 --skill completion-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: completion-status
Source: https://github.com/jedrecord/hal2026/tree/main/skills/completion-status
Command: npx skills add https://github.com/jedrecord/hal2026 --skill completion-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes how teams report progress on multi-step workflows by providing a clear, consistent set of completion statuses and an escalation format.

Core Features & Use Cases

  • Provides predefined statuses (DONE, DONE_WITH_CONCERNS, BLOCKED, NEEDS_CONTEXT) to communicate progress clearly.
  • Includes escalation guidelines to escalate when scope, confidence, or capability issues arise.
  • Ensures consistent status reporting across tasks, milestones, and projects to improve visibility and accountability.

Quick Start

After completing a milestone, set the status to DONE or BLOCKED and include any escalation notes.

Frequently Asked Questions about completion-status

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

FAQPage Schema
How do I standardize task status reporting for multi-step project workflows?

Standardize task status reporting by emitting predefined labels like DONE, BLOCKED, or NEEDS_CONTEXT across project tasks and sprint work to ensure consistent progress tracking and accountability.

What is the best way to flag workflow escalation when project risks arise?

Flag workflow escalation by applying the DONE_WITH_CONCERNS or BLOCKED status and appending explicit escalation notes to communicate scope, confidence, or capability issues immediately.

When do I need to use the NEEDS_CONTEXT status for milestone tracking?

Use the NEEDS_CONTEXT status for milestone tracking when a workflow step lacks necessary information to proceed, ensuring the blockage is clearly communicated for quick resolution.

Can I apply these predefined completion statuses to sprint work and knowledge tasks?

Yes, you can apply these predefined completion statuses uniformly across project tasks, sprint work, and knowledge tasks to maintain visibility and standardized reporting throughout the lifecycle.

Does this workflow status reporting approach work without external project management dependencies?

Yes, this workflow status reporting approach works without external project management dependencies, providing a standalone structure for standardizing completion labels and escalation formats.