coordinator

Track project decisions and changes across sessions via STATUS.md, CHANGELOG.md, and DECISIONS.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/LadderChaos/tora-skills --skill coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinator
Source: https://github.com/LadderChaos/tora-skills/tree/main/coordinator
Command: npx skills add https://github.com/LadderChaos/tora-skills --skill coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill maintains project context, tracks changes, and ensures collaboration coherence across sessions, enabling teams to stay aligned as work evolves.

Core Features & Use Cases

  • Context Continuity: Keep awareness of recent changes, decisions, and pending work across sessions.
  • Change Tracking: Maintain a living log of what was modified and why.
  • Collaboration Sync: Ensure a consistent understanding among participants during handoffs.
  • Decision Memory: Document architectural decisions and their rationale for future reference.
  • Artifacts: Produce and maintain STATUS.md, CHANGELOG.md, and DECISIONS.md to reflect current state and history.

Quick Start

Start a coordination session by reading STATUS.md to understand the current state, review recent changes, and summarize priorities for the session. After work, update STATUS.md, CHANGELOG.md, and DECISIONS.md as needed, and add new ADRs if significant.

Frequently Asked Questions about coordinator

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

FAQPage Schema
How do I maintain project context and track decisions across sessions?

To maintain project context across sessions, track decisions and changes using structured documentation artifacts. Read STATUS.md at startup to grasp current state, then log modifications in CHANGELOG.md and architectural rationale in DECISIONS.md after work concludes.

What is the best way to document project handoffs and ensure collaboration sync?

The best way to document project handoffs is by maintaining living logs of modifications and their rationale. This ensures collaboration sync by providing consistent awareness of recent decisions and pending work through STATUS.md, CHANGELOG.md, and DECISIONS.md.

How do I track architectural decisions and their rationale for future reference?

Track architectural decisions and their rationale by maintaining a DECISIONS.md file. This provides decision memory for future reference, capturing context and reasoning behind significant changes to ensure coherence as the project evolves.

When do I need to update project status and change logs during development?

Update project status and change logs during session startups, major changes, handoffs, and unclear project states. After completing work, update STATUS.md, CHANGELOG.md, and DECISIONS.md as needed, adding new ADRs if significant modifications occur.

Can I use markdown files for project coordination without external dependencies?

Yes, you can use markdown files for project coordination without external dependencies. This approach produces and maintains STATUS.md, CHANGELOG.md, and DECISIONS.md to reflect current state and history, requiring no additional tools or components.