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

Help

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Command reference for Genesis Spec-Kit. Pass a command name for detailed help on that command.

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done 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.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

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 57 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 that skill's SKILL.md and present: its description, argument hint and flags, process summary, and natural-language triggers.

    line 11

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

Genesis Spec-Kit — Command Reference

If a command name was given

Read that skill's SKILL.md and present: its description, argument hint and flags, process summary, and natural-language triggers. If it doesn't exist: "Unknown command '{name}'. Run /genesis-help for the full list."

Otherwise, print the full reference

# Genesis Spec-Kit

A spec-driven development pipeline. Features travel gated phases from idea to
shipped code; a quality-audit loop runs to zero findings at every boundary.
All state lives in plain files under .genesis/.

## Pipeline (in order)

| Command | What it does |
|---|---|
| /genesis-brainstorm | Interactive ideation + decision capture at any boundary |
| /genesis-feature    | Write the feature design doc (WHY + SHAPE) |
| /genesis-specify    | Write the master spec (WHAT) + the micro-spec plan |
| /genesis-clarify    | Find and close holes in the spec before North Star |
| /genesis-northstar  | Write the perfect-world vision + quality dimensions |
| /genesis-micro      | Write all micro specs for one group |
| /genesis-implement  | Implement one micro spec → one commit → one PR |
| /genesis-a1..a5     | The five audit lenses (run per group, loop to zero) |
| /genesis-final      | The F-pass: the lenses feature-wide + Dreamland + Simulation |
| /genesis-accept     | The boundary ritual — record approval, journal, advance (no git) |

### Audit order (per group): A1 → A2 → A3 → A4 → A5 (each loops to zero findings)
### The Double Gate: A3 cannot start until A1 is at zero findings.
### After all groups accepted: /genesis-final, then /genesis-closure (PR to main).

## Utility

| Command | What it does |
|---|---|
| /genesis-init       | Scaffold the kit and pick a mode |
| /genesis-discover   | Build the project profile through guided conversation |
| /genesis-constitute | Write the project's constitution (its supreme law) |
| /genesis-design     | Author project-level design docs (architecture, ADRs, journeys) |
| /genesis-amend      | Formally amend the constitution, with impact analysis |
| /genesis-closure    | Push the branch and open a PR (the only step that does git) |
| /genesis-status     | Where am I? (read-only, any time) |
| /genesis-resume     | Pick up where I left off (read-only, any time) |
| /genesis-help       | This reference |

## Quick start

1. /genesis-init        — set up the kit
2. /genesis-discover    — tell the kit about your project
3. /genesis-constitute  — define the rules
4. /genesis-brainstorm  — start your first feature

Natural language triggers

- "help"
- "what commands"
- "how do I"
- "command list"

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