agentleFS
Sign inStart free
codebycoreycodebycorey/delta-spec/skills/status/SKILL.md

status

Skill4 starsChanged 9 months agoMITView on GitHub

Show active changes with progress, dependencies, and next steps. Use when checking status, viewing active work, or reviewing the dependency graph.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 134 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Check if dependencies are still in specs/.delta/ (blocked) or archive/ (satisfied)

    line 26
  2. Distinctive:

    If any requirement has >1 change, display warning:

    line 37
  3. Very specific:

    If file exists, parse all ## Task N: sections

    line 49
  4. Very specific:

    If tasks.md doesn't exist, show "No tasks (run /ds:tasks)"

    line 54
  5. Distinctive:

    If a cycle exists, still show the graph (cycle will be visible in the structure)

    line 78
  6. Very specific:

    If no active changes, suggest running /ds:new <name>

    line 100

“Common” is measured: kept by at least 6 in 10 of the 134 edited versions of this file we could read. “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

/ds:status - Show active changes

Show status of all active changes.

Note: This skill is read-only and restricted to Read and Glob tools.

Step 0: Version Check

See version-check.md for the standard version compatibility check procedure.

Step 1: List active changes

List changes in specs/.delta/ (excluding archive/).

Step 2: Show change details

For each change, read the proposal and show:

  • Which artifacts exist (proposal? design? specs?)
  • Brief summary from proposal
  • Dependencies status:
    • Check if dependencies are still in specs/.delta/ (blocked) or archive/ (satisfied)
    • Show: ✓ ready or ⏳ blocked by: <change-name>
  • Next step (plan? tasks? ready to archive?)

Step 3: Detect conflicts

Scan all delta specs in active changes for overlapping modifications:

  1. For each change, read specs/.delta/<name>/specs/*.md
  2. Extract all MODIFIED and REMOVED requirement names
  3. Build map: requirement name → list of changes that touch it
  4. If any requirement has >1 change, display warning:
⚠️  Conflicts detected:
  "View Specifications" modified by: spec-search, other-change
  "Archive Change" modified by: archive-safety, breaking-change

Step 4: Show progress

For each change, read specs/.delta/<name>/tasks.md:

  1. If file exists, parse all ## Task N: sections
  2. Extract status from - **Status:** line for each task
  3. Count by status (pending, in_progress, done)
  4. Display: "Progress: 2/5 done" or "Progress: 0/5 pending"

If tasks.md doesn't exist, show "No tasks (run /ds:tasks)"

Step 5: Show dependency graph

Parse dependencies from all active changes and render ASCII tree.

Step 5.1: Detect Cycles

See cycle-detection.md for the cycle detection algorithm. Follow the Warn-only flow.

Step 5.2: Render Graph

Dependency Graph:
spec-search
└── status-enhancements
    └── archive-safety
plan-dependencies-fix (independent)
tasks-multi-change (independent)
  • Changes that other changes depend on are roots
  • Indent children (dependents) under their dependencies
  • Mark independent changes (no dependencies, nothing depends on them) explicitly
  • If a cycle exists, still show the graph (cycle will be visible in the structure)

Example Output

Active changes:

add-user-model
  Status: design + specs complete
  Summary: Add user schema for authentication
  Dependencies: None
  ✓ Ready to archive

add-oauth
  Status: proposal only
  Summary: Add social login with Google/GitHub
  Dependencies: add-user-model (active)
  ⏳ Blocked - run /ds:plan after add-user-model is archived

Notes

  • If no active changes, suggest running /ds:new <name>
  • Show clear next action for each change

Download now (ZIP)

  • Other versions166 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 166

    1. anthropics/claude-for-legal★ 9.5ksame name
    2. microsoft/TokenEconomizer★ 3.3ksame name
    3. zereight/gitlab-mcp★ 2.1ksame name
    4. indranilbanerjee/digital-marketing-pro★ 920same name
    5. H-mmer/pentest-agents★ 815same name
    6. me2resh/apexyard★ 532same name
    7. ffroliva/gflow-cli★ 350same name
    8. serithemage/serverless-openclaw★ 196same name
    9. atelier-fashion/adlc-toolkit★ 173same name
    10. backnotprop/bro★ 166same name

    156 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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 7 projects that use this

    • parallel-webSkill

      parallel-deep-research

      ONLY use when user explicitly says 'deep research', 'exhaustive', 'comprehensive report', or 'thorough investigation'. Slower and more expensive than parallel-web-search. For normal research/lookup requests, use parallel-web-search instead. Supports follow-ups with a known prior Task interaction ID.

      Also in 3 projects that use this

    • tim-mccrimmonSkill

      add

      Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.

      Also in 4 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 6 projects that use this

    • WelluxSkill

      rollback

      Execute or plan a deployment rollback. Invoke for: "rollback", "revert deployment", "undo deploy", "something broke in prod", "roll back to previous version", "deployment failed", "revert to v{version}".

      Also in 4 projects that use this

  • In this repository12 other files it gives its agents.

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