agentleFS
Sign inStart free
SatanshuMishraSatanshuMishra/interphase/skills/feature/SKILL.md

feature

Skill1 starsChanged 43 days agoApache-2.0View on GitHub

Use when the user wants something that does not exist yet, either a new capability or an extension of an existing one, and its intent, scope and success test are not yet pinned down.

71 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

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

  • 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 65 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read ${CLAUDE_PLUGIN_ROOT}/core/phases.md in full before any other action.

    line 10
  2. Distinctive:

    If phase 2 classifies the request as a different pathway, say so.

    line 13
  3. Very specific:

    If this conversation was summarized or cleared during this run, re-read docs/specs/<slug>.record.json, docs/specs/<slug>.decisions.md and …

    line 14

“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

Pathway: feature.

  1. The request is $ARGUMENTS, or the user's latest request when this skill started automatically.
  2. Read ${CLAUDE_PLUGIN_ROOT}/core/phases.md in full before any other action. Follow it with this pathway.
  3. The playbook is ${CLAUDE_PLUGIN_ROOT}/core/pathways/feature.md.
  4. The spec template is ${CLAUDE_PLUGIN_ROOT}/core/templates/spec-feature.md.
  5. If phase 2 classifies the request as a different pathway, say so. Then invoke the Skill tool with that pathway's skill instead.
  6. If this conversation was summarized or cleared during this run, re-read docs/specs/<slug>.record.json, docs/specs/<slug>.decisions.md and ${CLAUDE_PLUGIN_ROOT}/core/phases.md before acting.

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.

Reviews can't be read right now.

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