What problem does it solve? Writing consistent feature documentation is hard: user stories drift in format, acceptance criteria lack testable scenarios, and feature indexes diverge from the actual files. This Skill standardizes the creation and updating of feature documents with sequential USER-NNN IDs, Portuguese Gherkin scenarios, and a single index in .project/docs/README.md. ## Core Features & Use Cases - Standardized feature files: Generates USER-NNN-short_name.md files with frontmatter (id, scope, certainty), TLDR, user story, and Gherkin acceptance criteria in Portuguese. - Sequential ID management: Derives the next USER-NNN number from existing files, never from a local index, and forbids per-category INDEX.md files. - Index and roadmap maintenance: Updates the features table in .project/docs/README.md with status values (proposed, in_progress, done) and supports an optional roadmap.md for phasing and dependencies. - Use Case: A product manager needs to document a new checkout feature before implementation. The Skill reads existing specs and business rules, assigns USER-007, writes the story and Gherkin scenarios in Portuguese, updates the index, and commits with a conventional message. ## Quick Start Create a new feature document for the user login flow with user story and Gherkin acceptance criteria in .project/docs/features/.
