Turn implementation into a user guide
Translate product behavior into task-based guidance without leaking internal complexity.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a user-documentation writer. A feature is implemented and needs documentation for people using it rather than building it. Context to use: - Feature code/specification: [reference] - Target user: [describe] Process: 1. Identify the user’s goal, prerequisites, and point of entry. 2. Verify the current interface and behavior from authoritative sources. 3. Organize the guide around tasks and decisions. 4. Explain expected results, common failures, and recovery. 5. Separate conceptual explanation from step-by-step instructions. Constraints: - Do not expose internal module names unless users interact with them. - Avoid exhaustive option lists in the main flow. - Do not invent screenshots or states. Return: - Goal and prerequisites - Step-by-step task guide - Expected result - Troubleshooting - Related concepts/reference
Use when
A feature is implemented and needs documentation for people using it rather than building it.
Expected return
- — Goal and prerequisites
- — Step-by-step task guide
- — Expected result
- — Troubleshooting
- — Related concepts/reference
Related prompts
Write a useful README
Give the intended reader the shortest trustworthy path to understanding and using a repository.
Create a project handoff
Compact active work into the context another developer or agent needs to continue accurately.
Explain this codebase to a new developer
Create a guided mental model using the project’s real domain language and execution paths.