tpmo

Update project-state.json with milestones, deadlines, and prioritized task lists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Project Coordinator agent centralises roadmap, milestone, and deadline tracking for Heimdall and helps operators understand current status, next actions, and blockers without manual bookkeeping.

Core Features & Use Cases

  • Maintain authoritative project state: Owns and updates data/project-state.json with milestones, external deadlines, client progress, and blockers.
  • Prioritisation & orchestration: Determines next actions by analysing dependencies across agents and recommends agent assignments.
  • Status reporting: Produces concise markdown status summaries and escalation notes for stalled items such as grant or CVR prerequisites.
  • Use Case: When the operator asks "what's next?" the agent reads project-state.json, checks agent statuses and deadlines, and returns a prioritized worklist and any blocker escalations.

Quick Start

Ask the Project Coordinator for a current project summary and the single highest-priority unblocked action to work on next.

Frequently Asked Questions about tpmo

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

FAQPage Schema
How do I coordinate agent workflows and prioritize next actions for a project?

Project coordination involves analyzing dependencies across agents to determine next actions and recommend agent assignments. The coordinator evaluates project-state.json, agent statuses, and deadlines to produce a prioritized worklist.

How does roadmap milestone tracking work with project-state.json?

Roadmap milestone tracking uses project-state.json as an authoritative source to record milestones, external deadlines, client progress, and blockers. The coordinator updates this file to reflect current project status and surface stalled items.

Can I generate markdown status reports from agent status updates?

Yes, you can generate markdown status reports by reading agent status updates and docs/briefing.md. The coordinator produces concise status summaries and escalation notes for blockers like grant or CVR prerequisites.

What is the best way to surface blockers across multiple agent workflows?

Surfacing blockers requires centralizing deadline tracking and analyzing agent dependencies. The coordinator reads project-state.json, checks statuses, and returns escalation notes for stalled items in the generated markdown status report.

Do I need access to docs/briefing.md to maintain the project roadmap?

Yes, maintaining the project roadmap requires access to docs/briefing.md and agent status updates. The coordinator uses these inputs alongside ownership of data/project-state.json to prioritize tasks and produce worklists.

Why does project prioritization require analyzing dependencies across agents?

Project prioritization requires dependency analysis because agent tasks often block one another. Determining the highest-priority unblocked action requires checking agent statuses and deadlines against the current project-state.json.