add-task-status

Add task statuses across classic and runtime surfaces in agent-teams codebases.

27|1|Updated Jan 26, 2026

Search Tags:#task status #agent-teams #code auditing #status consistency #status application

Ready to run

npx skills add https://github.com/hua-bang/pulse-agent --skill add-task-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-task-status
Source: https://github.com/hua-bang/pulse-agent/tree/main/packages/agent-teams/harness/skills/add-task-status
Command: npx skills add https://github.com/hua-bang/pulse-agent --skill add-task-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit ensures that task, team, and agent statuses are consistently added and recognized across the agent-teams framework, avoiding potential issues with status mismatches and silent failures.

Core Features & Use Cases

Status Consistency: Helps maintain a single, unified status union for tasks, teams, and agents, ensuring that any new status is applied across both classic and runtime surfaces.
Status Audit: Guides the developer through auditing all areas in the codebase where status branching occurs, ensuring no silent-failure scenarios.
Guard and Rendering Updates: Ensures terminal status values are guarded correctly and renders correctly in the host environment.

Quick Start

Use the add-task-status Skill to add a new task status in your agent-teams codebase. For example, to add a 'new-status' to tasks, follow the instructions outlined in the SKILL.md.

Frequently Asked Questions about add-task-status

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

FAQPage Schema

How do I add a new task status in agent-teams without causing silent failures?▼

To add a new task status in agent-teams, you must audit all status-related branches in the codebase, update guard logic for terminal statuses, and ensure proper host rendering across classic and runtime surfaces to prevent silent failures.

Why are task statuses mismatched between classic and runtime surfaces in agent-teams?▼

Task status mismatches occur when new statuses are not consistently applied across both classic and runtime surfaces. Resolving this requires auditing all status-related code branches and updating terminal status guard logic.

What is the best way to ensure terminal status values are guarded correctly in agent-teams?▼

The best way to guard terminal status values is to audit all status-related code branches and update the guard logic to recognize the unified status union across classic and runtime surfaces.

Do I need to audit the entire codebase when adding a new agent status?▼

Yes, you need to audit all areas in the codebase where status branching occurs. This ensures any new agent status is recognized across classic and runtime surfaces without silent failures.

How do I update host rendering for a new task status in the agent-teams framework?▼

To update host rendering for a new task status, apply the status across classic and runtime surfaces and verify that terminal status guard logic correctly supports the rendering update.