write-a-readme

Generate a complete README document from scratch using a YAML frontmatter variant outline.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/mpsuesser/workspace --skill write-a-readme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-readme
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/opencode/skills/.todo/write-a-readme
Command: npx skills add https://github.com/mpsuesser/workspace --skill write-a-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning an idea into a useful README from scratch is hard and often results in missing context, unclear setup steps, or inconsistent structure. This Skill helps you draft a complete README by guiding you through a repeatable outline and variant-specific content.

Core Features & Use Cases

  • From-scratch README drafting: Start with a blank README and produce a structured first version.
  • Variant-driven organization: Adapt the README content based on the selected variant and progressively refine nested sections.
  • Optional documentation guidance: Use curated reference material (e.g., documentation systems and examples) to improve clarity and completeness.

Quick Start

Use the write-a-readme skill when you are asked to write a README from scratch and generate a first draft using the provided variant outline.

Frequently Asked Questions about write-a-readme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a README from scratch for a new project?▼

Generate a README from scratch by applying a structured outline that covers project overview, setup steps, and examples. This approach uses variant-aware instructions to produce a deterministic first draft, ensuring clear project onboarding documentation.

What is the best way to structure technical writing for project onboarding?▼

The best way to structure technical writing for project onboarding is to follow a repeatable outline that progressively refines nested sections. This ensures your README maintains consistent structure and covers necessary context and setup instructions.

Can I adapt README content for different project variants?▼

Yes, you can adapt README content for different project variants. This process uses variant-driven organization to iterate over nested sections, allowing you to progressively refine documentation based on the selected variant.

What should I include in a README when project documentation is incomplete?▼

When project documentation is incomplete, include a structured project overview, clear setup steps, and curated references. Using documentation systems and examples improves clarity and completeness, transforming a blank README into a useful first version.

Does this README generation approach require a specific format for instructions?▼

Yes, this README generation approach requires a YAML frontmatter with name and description, plus a body providing deterministic, variant-aware instructions. This format ensures the generated documentation structure remains consistent and accurate.