su-status

Extract project and task status from .ccb documentation and coordination files.

17|2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill su-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: su-status
Source: https://github.com/SeemSeam/agent-roles-spec/tree/main/roles/su-ccb/skills/su-status
Command: npx skills add https://github.com/SeemSeam/agent-roles-spec --skill su-status

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a quick and efficient way to determine the status of any project or task within the .ccb framework, helping you stay informed about progress and potential bottlenecks.

Core Features & Use Cases

  • Project and Task Status: Retrieve the current status of any project or task directly from the .ccb documentation and coordination files.
  • Custom Queries: Specify specific project IDs or task IDs to get detailed status updates on those items.
  • Information Retrieval: Read information on different phases like requirement analysis, technical design, task breakdown, dispatch, implementation, review, and archiving.

Quick Start

Run /ccb:su-status requirement_id=<id> to get the status of a specific requirement.

Frequently Asked Questions about su-status

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

FAQPage Schema
How do I track project status within the .ccb framework?▼

To retrieve task status from .ccb files, the Skill parses project documentation and coordination files to provide real-time updates on specific project or task IDs. You can run a command like /ccb:su-status requirement_id=<id> for detailed information.

What project phases does .ccb status tracking support?▼

Project status tracking supports multiple phases including requirement analysis, technical design, task breakdown, dispatch, implementation, review, and archiving. It reads this phase information directly from the .ccb documentation structure.

Do I need a structure-contract.yaml file to parse .ccb project status?▼

Yes, you need access to the .ccb framework files and the structure-contract.yaml file for accurate parsing. The structure-contract.yaml is required to correctly extract and interpret the project and task status information.

How do I query the status of a specific task ID in .ccb coordination files?▼

You can query the status of a specific task ID in .ccb coordination files by executing the command /ccb:su-status requirement_id=<id>. This retrieves detailed status updates for the specified item directly from the documentation.

Why is my .ccb status extraction not returning accurate project information?▼

If your .ccb status extraction is not returning accurate project information, it may be due to missing access to the required .ccb framework files or the structure-contract.yaml file. Accurate parsing depends on these structural dependencies being present.