agentleFS
Sign inStart free
sarveshtalelesarveshtalele/devcrew/.claude/skills/feature/SKILL.md

feature

Skill1 starsChanged 3 months agoMITView on GitHub

Drive one feature through all 15 SDLC pipeline stages using the department agents. Use for any non-trivial change. The orchestrator runs this; individual agents do not.

71 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bug, bugfix 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.
  • paulocsbSkill

    bug

    Investigation playbook for fixing a bug. Walks through 5 phases: reproduce → isolate → root cause → propose fix → validate. Forces concrete reasoning with code reads, log inspection, and git blame instead of pattern-matching guesses. Use for any non-trivial defect.

    Also in 8 projects that use this

  • team-attentionSkill

    bugfix

    Root cause based one-shot bug fix. debugger diagnosis → requirements.md generation → /execute. /bugfix "error description" Full investigation pipeline: debugger + gap-analyzer + standard verify. QA suggestion after successful fix.

    Also in 7 projects that use this

  • codebycoreySkill

    adopt

    Adopt an existing plan from conversation context into delta-spec format. Use when importing a plan, adopting planning that already happened, capturing plan mode output, or bringing in prior design work.

    Also in 4 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 10 projects that use this

  • marylinSkill

    recover

    Recover work from a crashed or interrupted session. Use when Claude crashed mid-task, after an unexpected exit, when you see 'stale sessions detected', or when you lost context and need to figure out what was happening.

    Also in 3 projects that use this

  • aegiswizardSkill

    context

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 65 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Read Project-Management.md §1 to get the current stage.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 65 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

Deliver this feature end to end: $ARGUMENTS

You are acting as orchestrator. Follow Project-Management.md §3 gates exactly.

Loop (repeat per stage)

  1. Read Project-Management.md §1 to get the current stage. Read nothing else.
  2. Spawn the stage's agents via the Agent tool — in parallel when independent (e.g. qa-engineer + e2e-automation; security-engineer + compliance-officer).
  3. Give each agent exactly: stage number, exit criteria, artifact paths it may touch, its token budget.
  4. Collect handoff blocks only.
  5. Evaluate exit criteria literally. fail → bounce to the authoring agent with the findings. blocked → resolve from the docs, else ask the user.
  6. On pass: update Project-Management.md §1, move tracker cards, append to Changelog.md.
  7. /clear before the next stage.

Fast path

For a change under ~20 lines with no new interface, no data-model change, and no security surface: stages 5→6→7→8 only. Log SKIPPED: 1-4,9 — trivial change, no contract or security surface in Changelog.md. Anything touching auth, payments, health data, uploads, deserialization, or an LLM is never eligible for the fast path.

Stop conditions

Committed secret · Critical vuln · PII/PHI/CHD leak · failed compliance control · third consecutive bounce-back on the same stage (escalate to the user instead of looping).

Output

Per stage: one line — stage N <name>: pass|fail — <artifact>. At the end: what shipped, what was skipped and why, total tokens.

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