How do I install the Standup Coordination skill?

Run npx skillmds@latest add tomevault-io/standup-coordination in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Standup Coordination safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Standup Coordination?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Standup Coordination free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Standup Coordination?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Standup Coordination by tomevault-io

Name: Standup Coordination
Author: tomevault-io

File contents

Standup.md Coordination Protocol

Reading standup.md

Always read standup.md at your configured standup location (e.g., ~/standup.md or your preferred path).

Look for:

DETAILED-TODO section - Current tasks to work on
Progress markers - Previous agent work (look for [worker HH:MM], [coworker HH:MM], [boss HH:MM])
Last completed task - Where to resume work
HARD TASKS section - Tasks that need escalation

Writing Progress Markers

When updating standup.md, use these exact formats:

In Progress

- [ ] task description <https://github.com/...>
  - [worker 10:15] IN PROGRESS: what you're doing

Done

- [x] task description <https://github.com/...>
  - [worker 10:23] DONE: brief completion summary, committed abc123

Failed

- [ ] task description <https://github.com/...>
  - [worker 10:45] FAILED: specific obstacle encountered, attempting retry

Boss Switch Decision

- [ ] task description <https://github.com/...>
  - [worker 10:45] FAILED: [obstacle description]
  - [boss 10:46] DECISION: switching to @coworker for [reason]
  - [coworker 10:47] IN PROGRESS: handling complex issue

Coordination Rules

Always prefix with [agent HH:MM] - Prevents conflicts between agents
Update after EACH task - Not at the end, immediately after completion
Include commit hash - Helps track what was saved
Be specific - "Fixed CSS flexbox" not "Fixed issue"
Check for new instructions - Read standup.md again if working for >10 minutes

Finding Next Task

Look for unchecked items [ ] without recent progress markers. If all items in a section have markers, check if they're complete or need retry.

Hard Tasks Section

If a task fails multiple times with both worker and coworker, add it to:

## HARD TASKS (Require user attention)

- [ ] [failed task description]
  - [worker 11:00] ATTEMPT 1: FAILED - reason
  - [coworker 11:30] ATTEMPT 2: FAILED - reason
  - STATUS: Needs user decision on approach

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: standup-coordinationdescription: Protocol for reading and writing progress markers in standup.md for multi-agent coordination Use when this capability is needed.---# Standup.md Coordination Protocol## Reading standup.mdAlways read standup.md at your configured standup location (e.g., `~/standup.md` or your preferred path).Look for:1. **DETAILED-TODO section** - Current tasks to work on2. **Progress markers** - Previous agent work (look for [worker HH:MM], [coworker HH:MM], [boss HH:MM])3. **Last completed task** - Where to resume work4. **HARD TASKS section** - Tasks that need escalation## Writing Progress MarkersWhen updating standup.md, use these exact formats:### In Progress```- [ ] task description <https://github.com/...> - [worker 10:15] IN PROGRESS: what you're doing```### Done```- [x] task description <https://github.com/...> - [worker 10:23] DONE: brief completion summary, committed abc123```### Failed```- [ ] task description <https://github.com/...> - [worker 10:45] FAILED: specific obstacle encountered, attempting retry```### Boss Switch Decision```- [ ] task description <https://github.com/...> - [worker 10:45] FAILED: [obstacle description] - [boss 10:46] DECISION: switching to @coworker for [reason] - [coworker 10:47] IN PROGRESS: handling complex issue```## Coordination Rules1. **Always prefix with [agent HH:MM]** - Prevents conflicts between agents2. **Update after EACH task** - Not at the end, immediately after completion3. **Include commit hash** - Helps track what was saved4. **Be specific** - "Fixed CSS flexbox" not "Fixed issue"5. **Check for new instructions** - Read standup.md again if working for >10 minutes## Finding Next TaskLook for unchecked items `[ ]` without recent progress markers. If all items in a section have markers, check if they're complete or need retry.## Hard Tasks SectionIf a task fails multiple times with both worker and coworker, add it to:```markdown## HARD TASKS (Require user attention)- [ ] [failed task description] - [worker 11:00] ATTEMPT 1: FAILED - reason - [coworker 11:30] ATTEMPT 2: FAILED - reason - STATUS: Needs user decision on approach```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/chektien) — claim your Tome and manage your conversions.

Frequently asked questions

Standup Coordination