Codex MCAF Feature Spec for Executable Acceptance Criteria
Write a concrete feature spec with scope, numbered business rules, main and failure flows, and repeatable verification.
中文Install in Codex
Codex with PrompterOne or a project using the MCAF conventions, its feature template, and the intended behavior.
- Copy the entire pinned `.codex/skills/dotnet-mcaf-feature-spec/` directory to `.agents/skills/dotnet-mcaf-feature-spec/` in the target checkout.
- Open Codex in that checkout and invoke `$dotnet-mcaf-feature-spec` with the example task and desired output.
Example task
Invoke `$dotnet-mcaf-feature-spec` for restoring archived notes in a practice project. Define observable results for a repeated restore and a failed restore.What to check
The spec records normal and failure behavior with acceptance criteria that map to user actions or automated tests.
Original SKILL.md on GitHub · Updated
Frequently asked question
When does a feature also need an architecture decision?
Document a new dependency, boundary, or long-term policy in an architecture decision when applicable and link it from the feature spec.