Author or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under docs/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under docs/stories/ — even if th
El comando exacto puede variar según el repositorio. Consulta el README en GitHub.
Para el autor de la skill
Pega en el README de tu repo
Muestra que tu skill está catalogada en Skillteca, genera backlink y tráfico rastreable.
[](https://www.skillteca.com.br/skills/doccraft-story?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Recibe nuevas skills de Escrita e Conteúdo todos los lunes
Un email corto con solo las skills nuevas de Escrita e Conteúdo. 4 minutos de lectura, sin spam, te das de baja con un clic.
Confirmas tu email en el primer envío. Sin spam. Te das de baja con un clic.
Managed by doccraft — doccraft update regenerates this file. Local edits will be overwritten. See doccraft.json to override project-specific vocabulary and paths without touching this file.
doccraft — planning stories
When to use
Creating a new story in docs/stories/.
Updating status, acceptance criteria, tags, or openspec on an existing story.
When closing a story: update docs/queue.md and the Status
column in docs/backlog.md. See Workflow reminders for
[Description truncada. Veja o README completo no GitHub.]
