idea-to-design-doc

idea-to-design-doc is a skill for Claude Code, Codex from AkoliteZA/hermes-agent-idea-workflow. It costs 29 tokens per session (1,422 once invoked), scanned A, original, MIT.

A guided process for turning a rough app idea into a focused product and design document. It asks questions about the intended users, experience, behavior, and practical shape of the product.

In plain words
What is it for?
Use it to capture ideas, maintain an ideas index, interview the idea's owner, and create a Markdown design document for later implementation.
Why use it?
It helps clarify what should be built before detailed coding or technical architecture begins. It keeps product goals and design decisions in one reusable note.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to capture ideas, maintain an ideas index, interview the idea's owner, and create a Markdown design document for later implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add AkoliteZA/hermes-agent-idea-workflow --skill idea-to-design-doc
Clone the repo
git clone --depth 1 https://github.com/AkoliteZA/hermes-agent-idea-workflow

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for idea-to-design-doc

README.md
[![agentmods](https://agentmods.dev/badge/skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc/github.svg)](https://agentmods.dev/skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc)
Your own site
<a href="https://agentmods.dev/skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc"><img src="https://agentmods.dev/badge/skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for idea-to-design-doc

Your own site · 80×15
<a href="https://agentmods.dev/skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc"><img src="https://agentmods.dev/badge/skills/akoliteza/hermes-agent-idea-workflow/idea-to-design-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,422 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01422
Opus 5 $0.00015 $0.00711
Sonnet 5 $0.00006 $0.00284
Haiku 4.5 $0.00003 $0.00142

Measured 11d ago against content hash c0b6b642b9de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

idea-to-design-doc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

idea-to-design-doc/SKILL.md · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

  1. A master ideas index
  2. One markdown note per idea
  3. A guided interview that stops when the user says stop, that's enough, or done
  4. 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.

Read the full file on GitHub · 189 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 189 lines · 29 tokens per session scan A c0b6b642b9de

Subscribe to this mod's changes

idea-to-design-doc is a skill published in the GitHub repository AkoliteZA/hermes-agent-idea-workflow (267 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,422 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

architecture-diagram

Generate architecture diagrams as fully editable SVG with native AWS, Azure, and GCP icons for cloud diagrams, or hand-drawn generic icons for everything else. Optionally deliver a self-contained editable draw.io mxGraph companion. Deterministic layout computes zone nesting and orthogonal routing instead of…

Mathews-Tom/armory · 162 tokens

concept-to-image

Turn concepts into static HTML visuals exported as PNG or SVG files via HTML/CSS/SVG. Triggers on: "create an image of", "export as PNG", "save as SVG", "concept to image", "screenshot this HTML". NOT for interactive HTML, use static-web-artifacts-builder.

Mathews-Tom/armory · 66 tokens

tldraw

Generate hand-drawn whiteboard-style diagrams (.tldr) from natural language and export to PNG/SVG via tldraw-cli, with vision-based self-check and an iterative review loop. Covers flowcharts, sequence diagrams, ERDs, UML sketches, and ML model diagrams. Triggers on: "whiteboard diagram", "sketch this out", "tldraw…

Mathews-Tom/armory · 128 tokens

ux-expert

UX design expert for auditing and redesigning pages, dashboards, and data-dense interfaces via 4-phase collaborative reviews across 8 UX dimensions. Triggers on: "review UX", "audit this page", "redesign the dashboard", "UX review", "improve the layout", "dashboard UX audit", "component recommendations".

Mathews-Tom/armory · 71 tokens

static-web-artifacts-builder

Build self-contained static HTML artifacts opened in a browser: interactive diagrams, dashboards, infographics. Pure HTML5+CSS3+inline SVG, zero toolchain. Triggers on: "interactive HTML", "open in browser", "HTML artifact", "visual dashboard", "HTML infographic". NOT for PNG/SVG output, use concept-to-image.

Mathews-Tom/armory · 76 tokens

taste

Use when improving the visual taste, positioning, polish, trust, and conversion clarity of a website or product UI. Runs a category-first visual audit, applies a decisive design pass, and verifies the result with screenshots rather than subjective vibes.

tryproduck/produck-skills · 49 tokens