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

sdlc-init

Skill1 starsChanged 3 months agoMITView on GitHub

Initialize a new SDLC project with ID, directory structure, and template files

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. GulajavaMinistudio/awesome-copilot-id★ 92same name
    2. ReStartAllKill/skills★ 2same 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create the SDLC skeleton documents and directory structure for a new project.

    line 10
  2. Very specific:

    Read docs/sdlc/index.md, parse existing PRJ numbers, and assign the next one (e.g.

    line 21
  3. Distinctive:

    Create the project directory:

    line 25

≈ “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 Initialization

Create the SDLC skeleton documents and directory structure for a new project.

Arguments

$ARGUMENTS format: <project-short-name> [priority P0/P1/P2]

  • Project short name: hyphen-separated English short name, e.g. resume-scoring-v2
  • Priority: optional, defaults to P1

Instructions

  1. Read docs/sdlc/index.md, parse existing PRJ numbers, and assign the next one (e.g. PRJ-001, PRJ-002...)
  2. Extract the project short name and priority (default P1) from $ARGUMENTS
  3. Create the project directory:
    docs/sdlc/PRJ-xxx-<short-name>/
    docs/sdlc/PRJ-xxx-<short-name>/reviews/
  4. Create docs/sdlc/PRJ-xxx-<short-name>/status.md:
    # PRJ-xxx: <Project Name>
    
    **Phase**: Phase 1 — BRD
    **Status**: 🟡 In Progress
    **Priority**: <priority>
    **Created**: <today's date>
    **Last Updated**: <today's date>
    
    ## Task Checklist
    
    ### Phase 1: BRD
    - [ ] PM researches and writes BRD
    - [ ] User reviews BRD
    - [ ] TPM reviews BRD
    - [ ] Engineer Lead reviews BRD
    
    ### Phase 2: Tech Design
    - [ ] Engineer Lead writes technical design
    - [ ] User reviews technical design
    - [ ] TPM reviews technical design
    
    ### Phase 3: Implementation
    - [ ] Task decomposition and dependency ordering (TPM)
    - [ ] Code implementation (Engineer Lead)
    - [ ] Code self-testing passes
    
    ### Phase 4: Testing & Bug Fix
    - [ ] QA Team review
    - [ ] PM functional acceptance
    - [ ] Bug fixes completed
    - [ ] QA sign-off
    - [ ] PM sign-off
    
    ### Phase 5: Launch Readiness
    - [ ] TPM launch readiness report
    - [ ] User final sign-off
    - [ ] Engineer Lead confirmation
    - [ ] PM confirmation
    
    ## Risk Register
    
    | ID | Risk Description | Impact | Probability | Mitigation | Status |
    |----|------------------|--------|-------------|------------|--------|
    
    ## Decision Log
    
    | ID | Decision | Date | Decision Maker |
    |----|----------|------|----------------|
    
    ## Blockers
    
    No current blockers.
  5. Create docs/sdlc/PRJ-xxx-<short-name>/brd.md:
    # BRD: <Project Name>
    
    **Project ID**: PRJ-xxx
    **Author**: PM Agent
    **Status**: Draft
    **Date**: <today's date>
    
    ## 1. Background & Problem Statement
    [To be filled by PM]
    
    ## 2. Goals & Success Criteria
    [To be filled by PM — must be measurable]
    
    ## 3. Scope
    ### In-Scope
    ### Out-of-Scope
    
    ## 4. Functional Requirements
    | REQ ID | Description | Priority |
    |--------|-------------|----------|
    
    ## 5. Dependencies & Constraints
    
    ## 6. Risks & Mitigation
  6. Append a row to the table at the end of docs/sdlc/index.md:
    | PRJ-xxx | <Project Name> | Phase 1 — BRD | 🟡 In Progress | <today's date> | <today's date> |
  7. Output confirmation:
    • Project ID and directory path
    • Next step: ask PM Agent to write the BRD (provide invocation suggestion)

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.