PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
A skill your agent uses when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
Install Idea To Design Doc
$ npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AkoliteZA/hermes-agent-idea-workflow idea-to-design-doc --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/idea-to-design-doc .claude/skills/idea-to-design-doc && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "idea-to-design-doc" agent skill from https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-doc into .claude/skills/idea-to-design-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "idea-to-design-doc", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-docType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AkoliteZA/hermes-agent-idea-workflow idea-to-design-doc --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/idea-to-design-doc .agents/skills/idea-to-design-doc && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "idea-to-design-doc" agent skill from https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-doc into .agents/skills/idea-to-design-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "idea-to-design-doc", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AkoliteZA/hermes-agent-idea-workflow idea-to-design-doc --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/idea-to-design-doc .cursor/skills/idea-to-design-doc && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "idea-to-design-doc" agent skill from https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-doc into .cursor/skills/idea-to-design-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "idea-to-design-doc", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AkoliteZA/hermes-agent-idea-workflow.git --path idea-to-design-doc--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AkoliteZA/hermes-agent-idea-workflow idea-to-design-doc --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/idea-to-design-doc .gemini/skills/idea-to-design-doc && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "idea-to-design-doc" agent skill from https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-doc into .gemini/skills/idea-to-design-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "idea-to-design-doc", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AkoliteZA/hermes-agent-idea-workflow idea-to-design-docInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/idea-to-design-doc .github/skills/idea-to-design-doc && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "idea-to-design-doc" agent skill from https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-doc into .github/skills/idea-to-design-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "idea-to-design-doc", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AkoliteZA/hermes-agent-idea-workflow idea-to-design-doc --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/idea-to-design-doc .opencode/skills/idea-to-design-doc && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "idea-to-design-doc" agent skill from https://github.com/AkoliteZA/hermes-agent-idea-workflow/tree/main/idea-to-design-doc into .opencode/skills/idea-to-design-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "idea-to-design-doc", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
idea-to-design-doc- GitHub stars
- 272
- Token cost
- ~1.6k tokens
- SKILL.md length
- 806 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
- Works in 4 steps: A master ideas index → One markdown note per idea → A guided interview that stops when the… → …
- Turning a rough idea into a focused product/design Markdown doc through guided questions
- SKILL.md covers Goal, Important constraints, Default storage layout and Lite vs Full mode, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Idea To Design Doc is an agent skill from AkoliteZA/hermes-agent-idea-workflow. Use when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records. The repository describes itself as: Pre-build idea-to-spec workflow skills for Hermes Agent: turn rough ideas into design docs, implementation specs, and Superpowers-ready build handoffs. The licence is MIT.
When your agent uses it
- Turning a rough idea into a focused product/design Markdown doc through guided questions
- Without moving into implementation too early
Example prompts
- “/idea-to-design-doc”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- A master ideas index
- One markdown note per idea
- A guided interview that stops when the user says stop, that's enough, or done
- The product idea, philosophy, intended experience, and practical technical shape needed to understand the app
What it can do on your machine
Read from SKILL.md and the folder at commit acf82c9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Idea To Design Doc loads about 1.6k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 806 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AkoliteZA/hermes-agent-idea-workflow at commit acf82c9, republished under its MIT licence (© AkoliteZA). 806 words, ~1,568 tokens.
Download SKILL.mdSave it as
.claude/skills/idea-to-design-doc/SKILL.md (or your agent's skills folder).- name
- idea-to-design-doc
- description
- Use when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
- version
- 1.1.0
- author
- Hermes Agent
- license
- MIT
Idea to Design Doc Workflow
Use this skill when the user says things like:
- "I have an idea for an app"
- "Help me flesh out this product"
- "Turn this thought into a design doc"
- "Make me a list of ideas and link each one to a note"
Goal
Convert a rough idea into a structured design document with:
- A master ideas index
- One markdown note per idea
- A guided interview that stops when the user says
stop,that's enough, ordone - The product idea, philosophy, intended experience, and practical technical shape needed to understand the app
This workflow starts with product thinking and only moves into technical aspects after the concept/philosophy is clear. The design doc should capture what the user wants and enough technical direction to support a later build plan.
Important constraints
- Do not push into backend, frameworks, database design, or code architecture too early.
- First capture product intent, behavior, audience, layout, features, UX, and philosophy.
- Then, when drafting the design doc, include the relevant technical aspects: platform assumptions, major system components, data needs, integrations, constraints, and likely architecture questions.
- For Full mode or build-bound ideas, recommend sensible technical defaults first, then let the user accept or change them. Cover database/storage, hosting/deployment, backend/runtime, frontend/UI, auth, platform targets, and other technical pieces only after the product direction is clear.
- Ask one question at a time when possible.
- If the user gives a short answer, follow up with a narrower question.
- If the user says to stop, immediately draft the note from what you have.
Default storage layout
Save files locally first, rather than directly into the Obsidian vault.
Recommended local folder structure:
./ideas/Ideas Index.md./ideas/<idea-title>.md
If the user later wants Obsidian export, treat that as a separate export step.
Lite vs Full mode
Use Lite mode for quick idea capture: ask only enough to produce a useful note. Use Full mode when the user wants a durable design doc or eventual implementation handoff.
The user can force the next stage with the exact phrase GREENLIGHT NEXT STAGE. If they use it, stop questioning, draft with current information, and record gaps under Open questions.
Interview flow
Ask questions in this order, adapting to the user's answers. For stronger prompts, use idea-superpowers-suite/references/interview-question-bank.md:
- Working title
- "What should we call this idea for now?"
- Problem / purpose
- "What problem does it solve, or what is it for?"
- Audience
- "Who is it for?"
- Core behavior
- "What should it do when someone uses it?"
- Primary user flow
- "What is the main thing a user should be able to do from start to finish?"
- Key features
- "What are the must-have features?"
- Layout / organization
- "How should the main parts be arranged or grouped?"
- Data location / hosting preference
- "Should the data stay local, be self-hosted, go to Cloudflare/AWS/another cloud, or is that undecided?"
- Platform targets
- "Should this be web-only, or should it also have a Windows app, Mac app, cross-platform desktop app, mobile app, or responsive mobile web?"
- Recommended technical defaults
- "Based on this idea, I recommend these technical defaults:
<short stack summary>. Do you want to accept them or change any part?"
- Preferences / feel
- "Should it feel simple, playful, serious, fast, calm, etc.?"
- Non-goals
- "What should this not do?"
- Success criteria
- "How will you know this idea is good enough to move forward?"
Show full SKILL.md (244 more words)Show less
Interview style
Use prompts like:
- "Tell me more about that part."
- "What would happen next?"
- "Can you give an example?"
- "Is that a must-have or a nice-to-have?"
- "Do you want it to be simple or more feature-rich?"
If the user is unsure, offer lightweight options instead of open-ended pressure:
- "Do you want this to be more like a list app, an overview page, or a single-focus tool?"
- "Should users see everything at once, or step through it one section at a time?"
Stop condition
If the user says any of the following, stop interviewing and draft immediately:
- stop
- that's enough
- enough for now
- done
- draft it
- write it up
- GREENLIGHT NEXT STAGE
Output format
When drafting, produce a markdown note with this structure:
# <Idea Title>
## One-line summary
## Problem / purpose
## Product philosophy
## Target user
## Core concept
## Desired behavior
## Key features
## Layout / information architecture
## UX / product notes
## Technical shape
## Data / integrations / platform needs
## Hosting / data location
## Platform targets
## Recommended technical defaults
## Non-goals
## Open questions
## Next stepsMaster index format
Maintain Ideas Index.md as a simple bullet list of idea notes:
# Ideas Index
- [[Idea Title]] — short one-line summary
- [[Another Idea]] — short one-line summaryIf the index file exists, append the new idea in alphabetical or newest-first order, but stay consistent.
Suggested response behavior
During the interview:
- Be conversational and concise.
- Ask a question, then wait for the user's answer.
- Keep the scope on product/design thinking.
When the user stops:
- Summarize the idea clearly.
- Capture uncertainties under Open questions.
- Save the note locally.
- Add/update the local index.
- Give the user the local note path.
Quality bar
A good result should make it easy to revisit the idea later and immediately understand:
- what it is
- who it is for
- how it should behave
- what matters most
- what is intentionally out of scope
© AkoliteZA, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in idea-to-design-doc of AkoliteZA/hermes-agent-idea-workflow.
Open the folder on GitHubat commit acf82c9
Compare with similar skills
Idea To Design Doc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Idea To Design Doc this skillAkoliteZA/hermes-agent-idea-workflow | 272 | — | ~1.6k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 7 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Architecture DecisionDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Architecture Decision
Donchitos/Claude-Code-Game-Studios
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
More from AkoliteZA/hermes-agent-idea-workflow
Idea Superpowers Suite
AkoliteZA/hermes-agent-idea-workflow
A skill your agent uses when running the full idea workflow: capture a rough idea, expand it into design/UI/implementation docs, research similar products, and generate build-ready Markdown artifacts.
Idea To Implementation Doc
AkoliteZA/hermes-agent-idea-workflow
A skill your agent uses when reviewing one specific idea/design doc, researching similar products, and producing a separate technical implementation plan or roadmap.
Idea To UI Design Brief
AkoliteZA/hermes-agent-idea-workflow
A skill your agent uses when turning a product/design doc into a focused UI design brief, optional AI image-generation concept prompts, and implementation-ready UI direction without replacing the…
Related
Categories
Questions about Idea To Design Doc
What does Idea To Design Doc do?
A skill your agent uses when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early. Idea To Design Doc is an agent skill from AkoliteZA/hermes-agent-idea-workflow. Use when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
When should I use Idea To Design Doc?
Idea To Design Doc fits situations like: turning a rough idea into a focused product/design Markdown doc through guided questions; without moving into implementation too early.
How do I install Idea To Design Doc in Claude Code?
Run `npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a claude-code`. Or copy the skill folder (idea-to-design-doc in AkoliteZA/hermes-agent-idea-workflow) into .claude/skills/idea-to-design-doc in your project. Claude Code loads it when a task matches its description.
How do I install Idea To Design Doc in Codex?
Run `npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a codex`. Or copy the skill folder (idea-to-design-doc in AkoliteZA/hermes-agent-idea-workflow) into .agents/skills/idea-to-design-doc in your project. Codex loads it when a task matches its description.
Can I use Idea To Design Doc in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/idea-to-design-doc, .gemini/skills/idea-to-design-doc, .github/skills/idea-to-design-doc and .opencode/skills/idea-to-design-doc in your project.
What does Idea To Design Doc need to run?
SKILL.md names no scripts, command-line tools or credentials: Idea To Design Doc is instructions for the agent only.
Does Idea To Design Doc access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Idea To Design Doc safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Idea To Design Doc use?
Idea To Design Doc is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Idea To Design Doc use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Idea To Design Doc?
Skills that share tags, products or a category with Idea To Design Doc: PR Design Doc (OpenHands/OpenHands, 91k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Domain Modeling (brim-borium/spotify_sdk, 166 stars) and Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Idea To Design Doc?
AkoliteZA (a GitHub user) maintains it in AkoliteZA/hermes-agent-idea-workflow, which has 272 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on May 5, 2026.
Source: AkoliteZA/hermes-agent-idea-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.