agentleFS
Sign inStart free
hlhr202hlhr202/swe-skills/skills/architect-status/SKILL.md

architect-status

Skill3 starsChanged 2 months agoApache-2.0View on GitHub

Report read-only Architect project status from core context and, when available, the tracks registry and plans. Use when the user asks for setup status, progress, current task, next action, blockers, completion percentage, or pending work.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep reads under safe architect/ paths and never resolve malformed track links.

    line 13
  2. Very specific:

    Read references/status-protocol.md and verify core context.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Architect Status

Report best-effort Architect state without changing it. Follow references/status-protocol.md as the source of truth.

Hard Boundaries

  • This skill is strictly read-only: never create, edit, move, delete, archive, or commit.
  • Keep reads under safe architect/ paths and never resolve malformed track links.
  • Report integrity issues; do not repair them.

Run

  1. Read references/status-protocol.md and verify core context.
  2. Classify missing, partial, or complete track-management state.
  3. Parse safe registry entries, plan task-status granularity, and metadata best-effort.
  4. Compute progress, current work, next action, blockers, and precedence-based project status.
  5. Return the concise report and stop without mutations or interactive cleanup prompts.

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.

Check your setup, free