Name: Draft how-to guide
Author: IanMadd

Prompt file imported from IanMadd/docs-skills (.github/prompts/draft-how-to.prompt.md). Copyright stays with the author.

Draft a how-to guide for a DevOps audience. Use the structure in doc-types.instructions.md and the style rules in docs-style.instructions.md.

Task: $input

Produce a focused, task-based guide with:

A title that starts with a bare infinitive verb: "Configure...", "Deploy...", "Set up..."
One or two sentences contextualizing when and why a reader would perform this task
A "Before you begin" section only if there are non-obvious prerequisites
Numbered steps, one action per step, each starting with an imperative verb
At least one code block showing an actual command or config, with the correct language identifier
The expected output or result after steps where it helps verify success
No conceptual explanations — if background is needed, add a  comment

Keep the guide under ten steps. If the task requires more, add a  comment at the point where it should be divided.

Draft a how-to guide for a DevOps audience. Use the structure in [doc-types.instructions.md](../instructions/doc-types.instructions.md) and the style rules in [docs-style.instructions.md](../instructions/docs-style.instructions.md). **Task**: $input Produce a focused, task-based guide with: - A title that starts with a bare infinitive verb: "Configure...", "Deploy...", "Set up..." - One or two sentences contextualizing when and why a reader would perform this task - A "Before you begin" section only if there are non-obvious prerequisites - Numbered steps, one action per step, each starting with an imperative verb - At least one code block showing an actual command or config, with the correct language identifier - The expected output or result after steps where it helps verify success - No conceptual explanations — if background is needed, add a `` comment Keep the guide under ten steps. If the task requires more, add a `` comment at the point where it should be divided.

{ "prompt": "Draft a how-to guide for a DevOps audience.\nUse the structure in [doc-types.instructions.md](../instructions/doc-types.instructions.md) and the style rules in [docs-style.instructions.md](../instructions/docs-style.instructions.md).\n\n**Task**: $input\n\nProduce a focused, task-based guide with:\n\n- A title that starts with a bare infinitive verb: \"Configure...\", \"Deploy...\", \"Set up...\"\n- One or two sentences contextualizing when and why a reader would perform this task\n- A \"Before you begin\" section only if there are non-obvious prerequisites\n- Numbered steps, one action per step, each starting with an imperative verb\n- At least one code block showing an actual command or config, with the correct language identifier\n- The expected output or result after steps where it helps verify success\n- No conceptual explanations — if background is needed, add a `` comment\n\nKeep the guide under ten steps.\nIf the task requires more, add a `` comment at the point where it should be divided.", "variables": [], "notes": "Draft a how-to guide for a specific DevOps task. Produces a task-based doc with prerequisites, numbered steps, and expected result. Use when the reader knows the context and needs the steps. Arguments: Describe the task — for example: set up a Kubernetes namespace with RBAC.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/IanMadd/docs-skills", "path": ".github/prompts/draft-how-to.prompt.md", "ref": "ae2f840b79f59939917e262b9c133b49d580a492", "url": "https://github.com/IanMadd/docs-skills/blob/ae2f840b79f59939917e262b9c133b49d580a492/.github/prompts/draft-how-to.prompt.md", "key": "IanMadd/docs-skills/.github/prompts/draft-how-to.prompt.md" } } }

Draft how-to guide

About

Use it

Manifest

Reviews