42 lines
1.2 KiB
Markdown
42 lines
1.2 KiB
Markdown
# HOWTO-FEATURE — Crear una feature con SDD y BDD
|
|
|
|
## Flujo corto
|
|
1. Crear ticket en backlog (`python3 scripts/new_ticket.py`)
|
|
2. `design` (architect)
|
|
3. `build` (implementer)
|
|
4. `review/security/qa`
|
|
5. `documentation_gate`
|
|
6. `close`
|
|
7. `publish` (`python3 scripts/publish_ticket.py --feature-id F-001`)
|
|
|
|
## Artefactos esperados
|
|
- `work/artifacts/<feature_id>/triage.md` (opcional)
|
|
- `work/artifacts/<feature_id>/architect.md` (opcional)
|
|
- `work/artifacts/<feature_id>/implementer.md`
|
|
- `work/artifacts/<feature_id>/reviewer.json`
|
|
- `work/artifacts/<feature_id>/security.json`
|
|
- `work/artifacts/<feature_id>/qa.json`
|
|
- `work/artifacts/<feature_id>/documenter.md`
|
|
- `work/artifacts/<feature_id>/leader-close.json`
|
|
- `work/artifacts/<feature_id>/publish.json`
|
|
|
|
## Ticket style
|
|
- English caveman
|
|
- short title
|
|
- short acceptance bullets
|
|
- clear scope in/out
|
|
|
|
## BDD notes
|
|
- Put `.feature` files in `spec/bdd/features/`
|
|
- Put steps in `features/steps/`
|
|
- Use tags like `@F-001`, `@smoke`, `@regression`
|
|
|
|
## Close rule
|
|
Feature can be `done` only if:
|
|
- review approved
|
|
- security approved
|
|
- qa approved
|
|
- documenter evidence exists
|
|
- publish evidence exists (`publish.json`)
|
|
- `./scripts/verify.sh` is green
|