status-update

Recompile STATUS.md from active audits, MVP plans, and ADRs.

Updated May 8, 2026
One-click install
npx skills add https://github.com/freire19/Mythos --skill status-update-freire19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-update
Source: https://github.com/freire19/Mythos/tree/main/skills/status-update
Command: npx skills add https://github.com/freire19/Mythos --skill status-update-freire19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps the project dashboard accurate by regenerating STATUS.md from the latest active documentation and by verifying whether listed high/critical fixes were actually applied in the codebase.

Core Features & Use Cases

  • Recompiles a single source of truth (STATUS.md): Reads the newest files from docs/audits/current/, docs/mvp/current/, and ADRs in docs/decisions/, then consolidates them into an at-a-glance project state.
  • Verifies issue resolution in real code: For each CRITICA/ALTA issue referenced by the docs, checks the referenced file/line and marks it as RESOLVIDO, EM PROGRESSO, or PENDENTE based on actual changes.
  • Supports planning and sprint visibility: Summarizes overall status, critical/open issues, recently resolved issues, audits coverage, current sprint progress, next sprint suggestions, and quick links to the relevant docs.

Quick Start

Run status-update to recompile docs/status with the latest audits, MVP plan, ADRs, and a real code verification of critical and high issues.

Frequently Asked Questions about status-update

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

FAQPage Schema
How do I automatically regenerate a project status dashboard from audit and MVP documents?

To regenerate a project status dashboard, recompile STATUS.md by scanning docs/audits/current, docs/mvp/current, and ADRs to consolidate the latest project state into a single source of truth.

How does issue verification work when tracking critical security audit findings in the codebase?

Issue verification works by correlating referenced CRITICA/ALTA issues from audit docs to specific file/line references, marking each as RESOLVIDO, EM PROGRESSO, or PENDENTE based on actual codebase changes.

What's the best way to keep ADR decisions and sprint progress visible in a live project dashboard?

Keep ADR decisions and sprint progress visible by recompiling STATUS.md to summarize overall status, critical issues, audit coverage, current sprint progress, and next sprint suggestions with quick links to relevant docs.

Do I need specific folder structures for audit reports and MVP plans to track project status?

Yes, project status tracking requires docs/audits/current for the latest Audit and DEEP_* reports, docs/mvp/current for the MVP plan, and docs/decisions for ADRs to recompile the dashboard accurately.

Can I verify if high-priority issues from documentation were actually fixed in the code?

Yes, you can verify high-priority issue fixes by checking each referenced file/line reference in the codebase against the CRITICA/ALTA issues listed in audit documents and updating statuses accordingly.

Why does my project status dashboard show outdated issue statuses after recent code changes?

Your dashboard shows outdated statuses because STATUS.md must be recompiled to verify whether referenced critical and high issues were truly fixed in the codebase after recent changes were applied.