Author or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under {{DOCS_DIR}}/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_DIR}}/stori
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-alexpialetski?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.
doccraft — planning stories
When to use
Creating a new story in {{DOCS_DIR}}/stories/.
Updating status, acceptance criteria, tags, or openspec on an existing story.
When closing a story: update {{DOCS_DIR}}/queue.md and the Status
column in {{DOCS_DIR}}/backlog.md. See Workflow reminders for
queue-audit invocation rules.
YAML frontmatter (required fields)
Use valid YAML between --- delimiters at the top of the file. Every
field marked yes MUST be prese
[Description truncada. Veja o README completo no GitHub.]
