agentleFS
Sign inStart free
NagiliantNagiliant/Genesis-Legacy-V2/skills/genesis-feature/SKILL.md

Feature

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Write the feature design doc — the WHY + SHAPE for a single feature. No formal requirements yet (those come in /genesis-specify).

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 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.
  • 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

4 rules. 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

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

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

    Write the feature design doc: why this feature exists, what shape it takes, how it fits the project.

    line 9
  2. Very specific:

    Create the feature branch (named for the feature) if not already on one, and create .genesis/features/<feature>/.

    line 25
  3. Very specific:

    Write design.md from feature-design-template.md.

    line 26
  4. Distinctive:

    Brownfield: add Existing System Analysis and a Scope Boundary Map (what changes vs what stays).

    line 34

“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

Feature — The WHY + SHAPE

Write the feature design doc: why this feature exists, what shape it takes, how it fits the project. It contains no formal requirements, acceptance criteria, or user stories — those come in /genesis-specify. This is the first per-feature pipeline command after that feature's brainstorm.

Gate: the feature's brainstorm phase must be accepted in approvals/master.json (else "Run /genesis-brainstorm and accept it first"). Also requires the project overview to exist.

Inputs

  • .genesis/project-state.md (mode)
  • The constitution
  • .genesis/design/overview.md (required), plus architecture.md, data-model.md, and other design docs
  • .genesis/features/<feature>/brainstorm-log.md (required)
  • .genesis/features/<feature>/approvals/master.json (verify brainstorm accepted)

Process

  1. Resolve the feature name; verify brainstorm accepted.
  2. Handle an existing/partial doc (revise vs continue vs fresh).
  3. Create the feature branch (named for the feature) if not already on one, and create .genesis/features/<feature>/.
  4. Write design.md from feature-design-template.md. Sections: Overview · Business Rules · User Experience · Edge Cases · Error Handling · Data Requirements · Security Considerations · Performance Considerations · System Diagram · Technology Choices · Design Decisions (institutional memory) · Scope · Future Considerations — plus mode-specific sections.
  5. Cross-reference project docs for contradictions and terminology; flag architectural discoveries that may require updating the project architecture doc.
  6. Self-validation pass (up to 3 iterations): flag vague business rules, missing mode-specific sections, scope creep beyond the brainstorm, contradictions with architecture, empty/placeholder sections; auto-correct and report.
  7. Constitution-compliance check; present for review; commit on the feature branch.

Mode differences

  • Greenfield: technical architecture / component breakdown.
  • Brownfield: add Existing System Analysis and a Scope Boundary Map (what changes vs what stays); use git blame for ownership.
  • Lowfield: process design — Pipeline Table Design, Artifact Schema Design, Domain Vocabulary.

Output

  • .genesis/features/<feature>/design.md — the WHY + SHAPE document.

Next step

Run /genesis-specify.

Natural language triggers

- "write the feature design"
- "shape this feature"
- "feature doc for X"

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