Technical design document draft
Draft a design doc with goals, options, a recommendation and risks, ready for team review.
Generate a practical README for a project: what it is, quick start, usage examples and contribution notes.
Write a README.md for this project.
Project name: {{name}}
What it does and who it is for: {{purpose}}
Language and tooling: {{language}}
Install and run steps as I know them: {{setup}}
Key features or API surface:
{{features}}
Tone: {{tone}}
Structure:
1. Title and a one-sentence description a stranger could understand in five seconds.
2. Why it exists: the problem and how this differs from the obvious alternatives, in at most four sentences. No marketing language.
3. Quick start: the shortest path from zero to a working result, as copy-pasteable commands, with expected output.
4. Usage: two or three realistic examples, from simple to more advanced, each with a code block.
5. Configuration: a table of options with defaults.
6. Project layout, only if it helps a newcomer.
7. Development: how to run tests and the linter, and how to contribute.
8. License and support section placeholders.
Only document what I have told you or what is evident from the input. Where information is missing, insert a clearly marked TODO rather than inventing commands, flags or badges. Verify that each step in the quick start follows from the one before it.The no-invention rule with TODO markers keeps the README accurate rather than confidently wrong. Paste your package manifest or main file as features for a more precise result.
Licensed CC0 (public domain) Version 1 · history
Draft a design doc with goals, options, a recommendation and risks, ready for team review.
Create a PR description that helps reviewers understand the change, how to test it and what to watch for.
Turn a diff or a rough description into a clean commit message that explains the why, not just the what.
Convert a rambling spoken transcript into a structured doc, keeping your ideas and voice while removing the noise.
Turn a rough description of how you do a task into a step-by-step SOP anyone on the team can follow.
Write a helpful FAQ for a page from real customer questions, with concise answers suited to readers and search snippets.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.