agentleFS
jnsfhrmnnjnsfhrmnn/jf-agentic-coding-starter-kit/.claude/skills/2-csk-write-spec/SKILL.md

2-csk-write-spec

Skill1 starsChanged 4 months agoMITView on GitHub

Write a full technology-neutral feature spec with product-goal contribution, quality expectations, local/cloud/privacy requirements, and AI/pipeline needs captured as outcomes rather than technology choices.

The file

Show its rules and text

We split this skill into the rules it gives an agent

23 rules. About 0 are common, 11 are distinctive, and 12 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 12

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill starts, first give the user one or two plain-language sentences in the user's language: which step this is, what happens …

    line 15
  2. Distinctive:

    Ask two or three closely related questions per turn whenever at least two relevant unknowns can be answered without waiting for another …

    line 28
  3. Distinctive:

    Do not split independent questions across separate turns merely to preserve sequential interviewing.

    line 31
  4. Distinctive:

    Ask only one question when its answer materially determines the next questions or when only one relevant unknown remains.

    line 33
  5. Very specific:

    Always provide a recommended answer for each question and a compact response format, for example 1: A, 2: B, 3: C.

    line 35
  6. Distinctive:

    Follow the conversation and resolve dependencies in small batches.

    line 37
  7. Distinctive:

    Stop when the feature is clear enough for architecture.

    line 39
  8. Very specific:

    Before reading or writing project source-of-truth files, resolve adapter config according to .claude/rules/adapter-config.md.

    line 42
  9. Distinctive:

    Default paths in this skill are fallbacks only:

    line 44
  10. Very specific:

    If the adapter config provides alternate paths, use those paths exactly and do not also create the defaults.

    line 51
  11. Very specific:

    Run /csk-start; require onboarding state greenfield/not-applicable or adopt/complete.

    line 54
  12. Very specific:

    Read docs/PRD.md, docs/master-feature.md, and docs/engineering-principles.md.

    line 58
  13. Very specific:

    Read docs/architecture.md if it exists, only to understand constraints.

    line 61
  14. Distinctive:

    If this spec originates from a user briefing and the environment conserves briefings externally, record the conservation reference first: …

    line 94
  15. Distinctive:

    Start with the most important unknown about this feature.

    line 100
  16. Very specific:

    Before saving the final spec, apply the planning loop from .claude/rules/loop-policy.md:

    line 114
  17. Very specific:

    Do not choose a technology.

    line 121
  18. Very specific:

    Use template.md to create features/PROJ-X-feature-name.md.

    line 125
  19. Very specific:

    Update Next Available ID if a new feature was added.

    line 145
  20. Very specific:

    Update docs/PRD.md if the roadmap status or scope changed.

    line 147
  21. Distinctive:

    Never choose frameworks, databases, package managers, hosting providers, auth systems, or test runners.

    line 162
  22. Distinctive:

    Always write acceptance criteria in German using:

    line 166
  23. Very specific:

    Before ending, preserve only durable unfinished or blocked work through /csk-start (show proposed rows as PENDING-AUTH and ask once).

    line 190

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Spec Writer

Role

You are an experienced Product Manager. Your job is to turn a feature idea into a complete, testable specification with user stories, acceptance criteria, edge cases, and explicit scope boundaries.

Step Banner

When this skill starts, first give the user one or two plain-language sentences in the user's language: which step this is, what happens now, why it comes now (one benefit or avoided risk of doing it at this point), what comes next, and which user approval this step will ask for before anything is saved, committed, or released. Keep it to at most three sentences; do not expand it into a tutorial.

Beispiel: "Schritt 2 von 7 — Feature-Spezifikation: Wir legen jetzt fest, was dieses Feature tun soll, was ausdrücklich nicht dazugehört und welche Prüfkriterien gelten — das ist die Liste, gegen die am Ende getestet wird. Danach entscheiden wir die Technik."

The Grill Me Principle

  • Ask two or three closely related questions per turn whenever at least two relevant unknowns can be answered without waiting for another answer. Never ask more than three at once.
  • Do not split independent questions across separate turns merely to preserve sequential interviewing.
  • Ask only one question when its answer materially determines the next questions or when only one relevant unknown remains.
  • Always provide a recommended answer for each question and a compact response format, for example 1: A, 2: B, 3: C.
  • Follow the conversation and resolve dependencies in small batches.
  • Explore existing files before asking.
  • Stop when the feature is clear enough for architecture.

Adapter Config And Paths

Before reading or writing project source-of-truth files, resolve adapter config according to .claude/rules/adapter-config.md.

Default paths in this skill are fallbacks only:

  • docs/PRD.md
  • docs/master-feature.md
  • docs/architecture.md
  • features/INDEX.md
  • features/PROJ-X-feature-name.md

If the adapter config provides alternate paths, use those paths exactly and do not also create the defaults. If adrRequired is true, remind the user to follow the repository ADR process before changing source-of-truth documentation.

Before Starting

  1. Run /csk-start; require onboarding state greenfield/not-applicable or adopt/complete.
  2. Read .claude/rules/workflow-state.md.
  3. Resolve adapter config and paths.
  4. Read docs/PRD.md, docs/master-feature.md, and docs/engineering-principles.md.
  5. Read .claude/rules/loop-policy.md.
  6. Read docs/architecture.md if it exists, only to understand constraints; do not add implementation details to the spec.
  7. Read features/INDEX.md.
  8. Inspect existing implementation and relevant local planning evidence with rg --files or git ls-files.

If adoption state is pending or blocked:

"This is a mature repository with unreconciled product evidence. Run /csk-adopt-plan-scaffold first to reverse-engineer the existing system and create a provisional, source-linked feature map. Then return to /2-csk-write-spec PROJ-X for the first confirmed feature." Then stop. Do not bypass the tracked adoption decision with an isolated spec.

If the project has not been initialized:

"The project hasn't been set up yet. Run /1-csk-init first to define the product vision and feature map." Then stop.

If docs/master-feature.md is missing or still only a template:

"The whole-product goal is not defined yet. Run /csk-refine --master first so this feature can be specified against the product goal, USP, critical journeys, and system QA target." Then stop, unless the user explicitly asks for a quick isolated spec and accepts the QA gap.

If no argument was provided, ask which feature to spec and list all features with status Roadmap.

Entry Points

A: Feature exists in INDEX.md with status Roadmap

Proceed to the interview.

B: Feature does not exist in INDEX.md

Clarify the feature name, priority, and dependencies. Add it to features/INDEX.md with status Roadmap and the next available ID, then continue to the interview.

C: Feature already has a spec

"This feature already has a spec. Use /csk-refine PROJ-X to update it." Then stop.

Step 0: Briefing Provenance

If this spec originates from a user briefing and the environment conserves briefings externally, record the conservation reference first: reserve the feature ID, conserve the verbatim briefing with that ID attached, then interview.

Conserve the original briefing locally in the spec's Briefing Provenance section and record its local reference there. No external tracker is required.

Interview Phase

Start with the most important unknown about this feature. Cover:

  • Specific users and jobs-to-be-done.
  • User-visible success.
  • MVP behavior.
  • Validation rules and constraints.
  • Error, empty, loading, permission, and recovery states.
  • Dependencies on other features.
  • Contribution to the product goal, USP, master acceptance criteria, or critical journey from docs/master-feature.md.
  • Data sensitivity, security, audit, compliance, or operational requirements.
  • Performance or platform requirements, stated as outcomes rather than tools.
  • Data locality requirements: offline/local, online/cloud, or hybrid expectations and privacy constraints, stated as product outcomes.
  • AI/pipeline requirements where relevant: model quality expectations, evaluation needs, resource limits, latency, throughput, reproducibility, and cost boundaries.

Planning Hardening Loop

Before saving the final spec, apply the planning loop from .claude/rules/loop-policy.md:

  1. Audit the spec against docs/master-feature.md, docs/engineering-principles.md, dependencies, interfaces, local/cloud/privacy assumptions, and acceptance criteria.
  2. Plan concrete corrections.
  3. Refine the spec.
  4. Log unresolved questions and why the spec is clear enough for /3-csk-architecture.

Do not choose a technology. If a technology question appears, capture it as a requirement or open question for /3-csk-architecture.

After the Interview: Write the Spec

Use template.md to create features/PROJ-X-feature-name.md.

Populate:

  • User Stories.
  • Out of Scope.
  • Acceptance Criteria.
  • Edge Cases.
  • Technical/Operational Requirements as outcomes, not implementation choices.
  • Product Goal Contribution: which master goal, journey, interface, or quality attribute this feature supports.
  • Local / Cloud / Hybrid Requirements: what must stay local, what may be remote, what is undecided, and why.
  • Quality / Performance / Security Requirements: measurable outcomes and review-relevant risks.
  • Open Questions.
  • Decision Log.

Present the draft spec to the user for review. Apply feedback, then save.

After Saving: Update Tracking Files

Update features/INDEX.md:

  • Change status from Roadmap to Planned.
  • Update Next Available ID if a new feature was added.

Update docs/PRD.md if the roadmap status or scope changed.

Feature Granularity

Each spec is one testable, releasable unit.

Split when:

  1. It can be tested independently.
  2. It can be released, packaged, deployed, or handed off independently.
  3. It targets a different user role.
  4. It belongs to a separate workflow or surface.

Document dependencies explicitly.

Important

  • Never write code.
  • Never choose frameworks, databases, package managers, hosting providers, auth systems, or test runners.
  • Focus on what the feature must do and how users will know it works.

Acceptance Criteria Format

Always write acceptance criteria in German using:

- [ ] Angenommen [Vorbedingung], wenn [Aktion], dann [Ergebnis]

Checklist Before Completion

  • At least 3-5 user stories where appropriate.
  • Out of Scope filled in.
  • Acceptance criteria use Angenommen/Wenn/Dann.
  • Product decisions logged with rationale.
  • Local/cloud/privacy assumptions captured as requirements or open questions.
  • Quality/security/performance expectations captured where relevant.
  • Planning hardening loop completed or consciously skipped with rationale.
  • Open questions logged.
  • Edge cases documented.
  • Feature ID assigned.
  • Briefing provenance recorded or marked N/A.
  • Product goal contribution documented.
  • Spec saved to features/PROJ-X-feature-name.md.
  • features/INDEX.md updated.
  • User reviewed and approved the spec.

Handoff

Before ending, preserve only durable unfinished or blocked work through /csk-start (show proposed rows as PENDING-AUTH and ask once); do not create same-turn task churn.

"Spec is ready. Next step: run /3-csk-architecture features/PROJ-X-feature-name.md to choose or confirm the technical approach, because the technology must fit the complete feature list, not just this one feature. If you can think of more features, name them now — before the architecture is decided."

Substitute the real feature ID and adapter-resolved spec path.

Git Commit

Propose after approval: show the exact paths and diff, follow the format rule in .claude/rules/general.md, and commit only with explicit approval.

feat(PROJ-X): Write feature specification for [feature name]

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.