Centralize project status updates across multiple documentation files.
npx skills add https://github.com/edumesones/azure--demo --skill status-reporter
Please help me install this Agent Skill. Skill: status-reporter Source: https://github.com/edumesones/azure--demo/tree/main/.claude/skills/status-reporter Command: npx skills add https://github.com/edumesones/azure--demo --skill status-reporter
This skill ensures a single source of truth for project status across all skills by centralizing status updates and logs, eliminating fragmented reporting and misaligned dashboards.
Call update_task_complete(feature_id, task_description) after finishing a task, or update_phase_complete(feature_id, phase_name) after completing a phase. Use update_blocker(feature_id, blocker_description) when blockers arise. Ensure all relevant docs reflect the new state.
High-intent search queries and answers about installing and using this skill.
You maintain consistent project status across multiple skills by centralizing updates across project-status.md, features index, and status-log.md into a single source of truth, eliminating fragmented reporting.
You record timestamped status changes for project auditability by appending entries to a unified action log in status-log.md, ensuring all task completions and blockers are tracked chronologically.
The best way to log project blockers and phase completions in markdown is to invoke standardized update functions that atomically update feature-specific docs and append timestamped records to status-log.md.
You do not need any external dependencies to synchronize project status dashboards, as this governance mechanism operates independently using standard markdown documentation files for atomic updates.
You update feature status docs automatically after finishing a task by calling update_task_complete with the feature ID and task description to propagate changes across the project dashboard.
You should avoid using a centralized status reporting workflow if your project does not require synchronized dashboards or if your team manages progress tracking entirely outside of markdown documentation files.
ImproperSubsetEnforce documentation governance rules for Markdown files and project structures.
brobertsazSave and recall timestamped, tagged memory entries in Memory MCP.
bamechoPlan and execute autonomous feature development with dependency-based task decomposition.
stephendorGenerate a Phase 0 status dashboard from project Markdown files.
