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
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/doccraft-story-alexpialetski?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Escrita e Conteúdo skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
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.]
