agentleFS
foliveirafoliveira/harmonia/skills/status/SKILL.md

status

Skill2 starsChanged 46 days agoMITView on GitHub

Harmonia status - a read-only readout of the active task's stage, markers, and receipts. Use ONLY when explicitly invoked as /harmonia:status.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

The file

Files
SKILL.md

This is a read-only readout: it writes nothing - no marker, no receipt, no workspace file.

  1. Resolve the active task:
bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh resolve --repo .

Surface resolve's own message and stop on its non-zero exits (exit 2 ambiguous active tasks; exit 3 no active task).

  1. From the resolved workspace dir (.harmonia/tasks/<id>/), report:
    • the active task id;
    • its lifecycle stage, derived by reading the artifact contract in ${CLAUDE_PLUGIN_ROOT}/core/lifecycle.yaml as data and matching which stage-boundary out-artifacts are present - do not hardcode a stage table;
    • which markers and receipts are set: scope.md, design.md, boundary.md, diff-summary.md, verdict.md, accepted, rejected, done, abandoned, and the receipts/ contents (check-criteria.json, criteria-run.json).

Report only what is on disk. It composes existing mechanisms into a readout and adds no new script.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.