mc-report

Report semantic milestones and artifacts to the Mission Control tracking system.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/vinceferro/claude-kickoff --skill mc-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mc-report
Source: https://github.com/vinceferro/claude-kickoff/tree/main/plugin/skills/mc-report
Command: npx skills add https://github.com/vinceferro/claude-kickoff --skill mc-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the visibility gap between mechanical agent activity and meaningful project progress by allowing agents to report semantic milestones, decisions, and artifacts directly to the Mission Control board.

Core Features & Use Cases

  • Semantic Reporting: Log high-level decisions, milestone completions, and blocking issues that the automated lifecycle hook cannot detect.
  • Artifact Linking: Associate completed workstreams with specific preview URLs, PR links, or screenshots to provide immediate proof of progress.
  • Use Case: When a design decision is finalized or a feature slice is deployed to a staging environment, use this skill to update the project board so the human operator can steer based on actual outcomes rather than just raw tool logs.

Quick Start

Use the mc-report skill to log that the payment integration is complete and provide the link to the new checkout page.

Frequently Asked Questions about mc-report

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

FAQPage Schema
How do I report project milestones to a tracking system in a multi-agent environment?

You report project milestones by using a semantic reporting skill to log high-level decisions and completed workstream statuses directly to the Mission Control tracking system. This updates the project board with meaningful progress rather than raw tool logs.

How do I link deployment artifacts like preview URLs to my project management board?

Linking deployment artifacts like preview URLs is done by associating completed workstreams with specific PR links or screenshots during the semantic report. This provides immediate proof of progress on the project board for human operators to review.

What is the best way to track design decisions automatically during project development?

Tracking design decisions automatically requires an agent to report finalized decisions and blocking issues to the Mission Control board. This bridges the visibility gap between mechanical agent activity and meaningful project progress for human steering.

Do I need write access to mission-control tracking files to log project status?

Yes, you need atomic write access to the project's mission-control tracking files to log project status. This access is required alongside integration with the local kickoff plugin lifecycle to facilitate the reporting workflow.

When should I use semantic project reporting instead of automated lifecycle hooks?

Use semantic project reporting when an automated lifecycle hook cannot detect high-level outcomes, such as a finalized design decision or a feature slice deployed to staging. It logs these semantic beats to provide actual outcome visibility.

Can I update a project board with staging environment links from a multi-agent workflow?

Yes, you can update a project board with staging environment links by reporting the completed workstream and associating the new checkout page URL or preview link as an artifact. This allows the human operator to steer based on actual deployment outcomes.