agentleFS
michaellam26michaellam26/pathfinder/.claude/skills/sdlc-status/SKILL.md

sdlc-status

Skill1 starsChanged 3 months agoMITView on GitHub

View SDLC project status - single project detail or all active projects overview

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. exerias21/brainstorm-toolkit★ 0same name

    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.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Use Glob to search docs/sdlc/PRJ-xxx-*/status.md to locate the corresponding project directory

    line 20
  2. Very specific:

    Read status.md and display:

    line 21
  3. Very specific:

    If brd.md, tech-design.md, or launch-readiness.md exist, indicate their status

    line 27
  4. Very specific:

    Check the reviews/ directory and list existing review records

    line 28
  5. Distinctive:

    If the index table is empty, display: "No active SDLC projects.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

SDLC Project Status View

View SDLC project status. Supports single project detail or global overview.

Arguments

$ARGUMENTS: optional project ID (e.g. PRJ-001)

Instructions

With project ID: Single project detail

  1. Use Glob to search docs/sdlc/PRJ-xxx-*/status.md to locate the corresponding project directory
  2. Read status.md and display:
    • Current phase and status
    • Task completion progress per phase (completed/total)
    • Risk register
    • Current blockers
    • Recent decision log entries
  3. If brd.md, tech-design.md, or launch-readiness.md exist, indicate their status
  4. Check the reviews/ directory and list existing review records

Without arguments: Global overview

  1. Read docs/sdlc/index.md
  2. If the index table is empty, display: "No active SDLC projects. Use /sdlc-init to create a new project."
  3. For each active project (status is not ✅ Complete), read its status.md and extract key information
  4. Generate a summary report:

    ## SDLC Project Status Overview
    
    **Date**: YYYY-MM-DD
    
    | Project ID | Name | Phase | Progress | Risks | Blockers |
    |------------|------|-------|----------|-------|----------|
    
    ### Projects Requiring Attention
    [List projects with risks or blockers; if none, note "All projects progressing normally"]

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.