docs-writer
Documentation workflow that converts requirements into structured AsciiDoc sections, runs Vale for style compliance, and produces merge-ready content. Use when creating or updating AsciiDoc documentation from Jira tickets, GitHub issues, or feature descriptions.
74
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Docs Writer Workflow Orchestrator
Quick Start
- If the user invoked a specific command (e.g.
/draft,/validate), readcommands/{command}.mdand follow it. - Otherwise, read
skills/controller.mdto load the workflow controller:- If a
ticket_idis known, check.artifacts/${ticket_id}/for existing artifacts and resume from the next incomplete phase (see "Resuming Work" in the controller) - If the user provided a Jira ticket, GitHub issue URL, or feature description, execute the
/gatherphase - Otherwise, execute the first phase the user requests
- If a
If a step fails or produces unexpected output, stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.
For principles, hard limits, safety, quality, and escalation rules, see guidelines.md.
- Repository
- amir-yogev-gh/ai-workflows
- Commit
f0e2c19
- Last updated
- Created
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.