write-project-document
/write-project-document
Create concise project documents in Markdown with the sections Problem, Solution, Scope, Rabbit Holes, and No Gos. Use when the user asks to draft, structure, or refine a project document, project brief, proposal, feature spec, or planning note in this specific Seed-style format.
- Author
- seed-hypermedia ↗
- Repository
- seed ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Create concise project documents in Markdown with the sections Problem, Solution, Scope, Rabbit Holes, and No Gos. Use when the user asks to draft, structure, or refine a project document, project brief, proposal, feature spec, or planning note in this specific Seed-style format.
Original author description
Create concise project documents in Markdown with the sections Problem, Solution, Scope, Rabbit Holes, and No Gos. Use when the user asks to draft, structure, or refine a project document, project brief, proposal, feature spec, or planning note in this specific Seed-style format.
How it works
- Output format
- Section guidance
- Working style
SKILL.md preview
--- name: write-project-document description: Create concise project documents in Markdown with the sections Problem, Solution, Scope, Rabbit Holes, and No Gos. Use when the user asks to draft, structure, or refine a project document, project brief, proposal, feature spec, or planning note in this specific Seed-style format. --- # Write Project Document Create comprehensive project document in Markdown with the sections Problem, Solution, Scope, Rabbit Holes, and No Gos based on the current context, draft, solution and scope in this specific session. publish the document as a Seed document in your organization's Hypermedia space rather than adding a file to the repository: write it to a temporary markdown file, then `seed-cli document create -f <file.md> -p /projects/<slug> --name "<Project title>" -k <key>` (add `--dry-run` first to validate), and share the resulting `hm://` link. The repository keeps only published reference documentation, under `hypermedia/`; a project document is a working record for the life of the project. When the project ships, fold any durable facts into the matching `hypermedia/` page. <support-material> ## Output format Always produce these sections in this order: ```markdown # <Project title> ## Problem ## Solution ## Scope ## Rabbit Holes ## No Gos ``` Use bullets when the content is easier to scan. Use paragraphs only where narrative explanation is clearer. ## Section guidance - **Problem**: State the user pain, product gap, or operational issue. Explain why it matters now. Avoid solution details unless needed for context. - **Solution**: Describe the proposed approach in concrete terms. Include the user-facing behavior and the system changes only at the level needed for planning. Define what will be included. Prefer crisp bullets that can later become implementation tasks or acceptance criteria. if you can also add user stories to it the better. - **Scope**: the timeframe it will require to implement the solution. if the plan is multi-phase or multi-step, you can define the timeframe for each one and also dependencies of each phase/section - **Rabbit Holes**: List tempting investigations, extensions, or refactors that could consume time but are not required for the first useful version. - **No Gos**: List explicit non-goals, constraints, and things the project should not do. ## Working style If inputs are sparse, draft a useful first version with clearly labeled assumptions instead of blocking. Ask clarifying questions only when a missing decision would materially change the project direction. Keep the document practical and opinionated. Favor specific statements over generic product-planning language. </support-material>
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named write-project-document.
Database snapshot: 13.11.2026 · package version 57818ec6afd7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90create-shape-up-pitch
Write a Shape Up pitch with problem, appetite, solution sketch, rabbit holes, and no-gos when the user asks to pitch a feature, shape work, or write a Shape Up proposal - 100write-brd
Write a practical Business Requirements Document (BRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, generate, refine, or save a BRD/business requirements document/product business… - 100write-prd
Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec,… - 86d2s-frame
Stage 1 (frame) of a discovery-to-spec design exploration. Turns a feature request, idea or stakeholder ask into a one-page brief covering the problem, who it matters to, where it lives in the product today, the desired outcome, the appetite and the no-gos. Use whenever someone… - 90writing-product-specs
Use when asked to write a product spec, PRD, or requirements document, or to design a new feature or project before implementation - interactively elicits problem, audience, success criteria, and scope, then produces a structured spec file - 100create-prd
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.