dotnet-skills Current release catalog-v2026.4.5.0
Skill page Architecture v1.0.0

MCAF: Feature Spec

Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

Trigger On

  • add or change non-trivial behaviour
  • behaviour is under-specified and engineers are guessing
  • tests need a stable behavioural source of truth

Workflow

  1. Define scope first: in scope, out of scope, boundaries touched.
  2. If the feature doc is missing, scaffold from references/feature-template.md.
  3. Keep the spec executable:

- numbered rules - main flow - edge and failure flows - system behaviour - verification steps - Definition of Done

  1. Make the spec concrete enough that tests can be written without guessing.
  2. If the feature creates a new dependency, boundary, or major policy shift, update an ADR too.

Deliver

  • docs/Features/feature-name.md
  • a feature spec that engineers and agents can implement directly

Validate

  • rules are testable, not aspirational
  • edge cases are captured where they matter
  • verification steps match the intended behaviour
  • the doc can drive implementation without hidden tribal knowledge

Load References

  • use references/feature-template.md only for scaffolding

Related skills