agentleFS
Sign inStart free
EffortlessMetricsEffortlessMetrics/demo-swarm/.claude/skills/feature/SKILL.md

feature

Skill0 starsChanged 9 months agoApache-2.0View on GitHub

Feature implementation workflow.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write tests alongside each implementation step, not at the end

    line 79
  2. Distinctive:

    Don't gold-plate - implement what's specified

    line 80

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

Feature Skill

Feature implementation workflow.

Input

Provide:

  • Feature description/spec
  • Acceptance criteria (if available)
  • Constraints or requirements

Workflow

1. Understand

- What problem does this solve?
- What are the inputs/outputs?
- What are the edge cases?
- What are the constraints?

2. Plan

- Break into implementable steps
- Identify files to create/modify
- Identify dependencies
- Estimate scope

3. Implement

For each step:

1. Write the code
2. Write tests for that code
3. Verify tests pass
4. Move to next step

4. Integrate

- Wire up to rest of system
- Update any configuration
- Update documentation if public API

5. Verify

- Run full test suite
- Manual verification of acceptance criteria
- Check for regressions

Output Format

## Feature
<description>

## Implementation
| Step | Files | Status |
|------|-------|--------|

## Tests Added
| Test | What it verifies |
|------|------------------|

## Evidence
- New tests: <count>
- Test suite: <pass/fail>
- Acceptance criteria: <met/unmet>

## Usage
<how to use the new feature>

## Limitations
<what's not included, known constraints>

Rules

  • For significant features, prefer /flow-1-signal through the full SDLC
  • Write tests alongside each implementation step, not at the end
  • Don't gold-plate - implement what's specified
  • Note but don't implement adjacent features
  • Document limitations explicitly

Download now (ZIP)

  • Other versions66 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 66

    1. crbnos/carbon★ 2.8ksame name
    2. aeonfun/aeon★ 782same name
    3. aaronjmars/aeon★ 776same name
    4. astashov/liftosaur★ 747same name
    5. me2resh/apexyard★ 532same name
    6. yicheng47/runner★ 376same name
    7. bradtraversy/coding-with-ai-course-resources★ 344same name
    8. garagon/nanostack★ 206same name
    9. DeL-TaiseiOzaki/claude-code-orchestra★ 194same name
    10. vide/matedroid★ 82same name

    56 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 bug, bugfix and 10 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.
    • marcusbelzSkill

      bug

      Document a bug as a single file under docs/bugs/. Use to report new bugs or update the status of existing ones.

      Also in 6 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 6 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

    • 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

    • AWSSkill

      map

      Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

      Also in 4 projects that use this

    • corygabrielsenSkill

      spike

      Implement N approaches as separate branches, then compare side-by-side. Removes "implementation effort" as a variable from the decision.

      Also in 4 projects that use this

  • In this repository21 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