agentleFS
Sign inStart free
typvtypv/nest-turbo-starter/.claude/skills/specs/SKILL.md

specs

Skill224 starsChanged 3 months agoMITView on GitHub

Analyze requirements, create/maintain FSD and use cases. Use for business analysis, requirements documentation, functional specs.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    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. Distinctive:

    Create and maintain Functional Specification Documents (FSD) and use case documentation through codebase analysis and requirements …

    line 9
  2. Very specific:

    If invoked without arguments, use AskUserQuestion to present available operations:

    line 13

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

Business Analysis

Create and maintain Functional Specification Documents (FSD) and use case documentation through codebase analysis and requirements engineering.

Default (No Arguments)

If invoked without arguments, use AskUserQuestion to present available operations:

OperationDescription
initAnalyze codebase & create FSD + use cases
analyzeAnalyze new feature requirements
updateSync FSD & use cases with codebase

Present as options via AskUserQuestion with header "Business Analysis", question "What would you like to do?".

Subcommands

SubcommandReferencePurpose
/specs initreferences/init-workflow.mdAnalyze codebase and create initial FSD + use cases
/specs analyze "feature"references/analyze-workflow.mdAnalyze new feature and update FSD + use cases
/specs updatereferences/update-workflow.mdSync FSD + use cases with current codebase state

Routing

Parse $ARGUMENTS first word:

  • init → Load references/init-workflow.md
  • analyze → Load references/analyze-workflow.md, pass remaining args as feature description
  • update → Load references/update-workflow.md
  • empty/unclear → AskUserQuestion

Shared Context

  • Detection script: .claude/skills/common/detect-project-type.sh
  • FSD template: references/templates/fsd-template.md
  • UC template: references/templates/use-case-template.md
  • PRD input: docs/project-overview-pdr.md
  • Output FSD: docs/project-fsd.md
  • Output UCs: docs/usecases/{module}/uc-{module}-{nnn}-{slug}.md

Note: This skill was previously named /ba. All references now use /specs.

IMPORTANT: Do not start implementing code. This skill produces documentation only.

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