A skill your agent uses when the user hands you a vague or half-formed feature ask and wants it turned into a lightweight PRD, or asks to "write a PRD", "spec this feature", "flesh this out", or…

MITAuto-check passedProduct & Project Management

Install Lite Prd

skills CLI
$ npx skills add ragnar-pwninskjold/tech-snacks --skill lite-prd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ragnar-pwninskjold/tech-snacks lite-prd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ragnar-pwninskjold/tech-snacks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/tech-snacks/skills/lite-prd .claude/skills/lite-prd && rm -rf skills-src

Use ~/.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/

Facts

Skill name
lite-prd
GitHub stars
137
Token cost
~853 tokens
SKILL.md length
444 words
Files
3 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user hands you a vague or half-formed feature ask and wants it turned into a lightweight PRD, or asks to "write a PRD", "spec this feature", "flesh this out", or…

  • Works in 4 steps: Set up the workspace → Interview by traversing the design tree → Synthesize the PRD → …
  • The user hands you a vague
  • SKILL.md covers What this does, Flags, Step 1 — Set up the workspace and Step 2 — Interview by…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lite Prd is an agent skill from ragnar-pwninskjold/tech-snacks. Use when the user hands you a vague or half-formed feature ask and wants it turned into a lightweight PRD, or asks to "write a PRD", "spec this feature", "flesh this out", or invokes /lite-prd. Interviews the user by traversing a design tree of clarifying questions, persists every Q&A round to the repo, and emits a lite-prd.md.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/prd-template.md` and `references/traversal-protocol.md`).

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: A skill library for vibe coders that make cool stuff. The licence is MIT.

When your agent uses it

  • The user hands you a vague
  • Half-formed feature ask and wants it turned into a lightweight PRD
  • Asks to write a PRD
  • Spec this feature

Example prompts

  • “write a PRD”
  • “spec this feature”
  • “flesh this out”
  • “/lite-prd”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Set up the workspace
  2. Interview by traversing the design tree
  3. Synthesize the PRD
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 2d9a73b. 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.

    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

Lite Prd loads about 853 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 444 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~853
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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 ragnar-pwninskjold/tech-snacks at commit 2d9a73b, republished under its MIT licence (© ragnar-pwninskjold). 444 words, ~853 tokens.

Download SKILL.mdSave it as .claude/skills/lite-prd/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
lite-prd
description
Use when the user hands you a vague or half-formed feature ask and wants it turned into a lightweight PRD, or asks to "write a PRD", "spec this feature", "flesh this out", or invokes /lite-prd. Interviews the user by traversing a design tree of clarifying questions, persists every Q&A round to the repo, and emits a lite-prd.md.

lite-prd

Turn a vague feature ask into a lightweight PRD by interviewing the user with AskUserQuestion, traversing the design tree (branch deeper when an answer opens new territory), persisting every round, and writing lite-prd.md.

What this does

  1. Reads the vague ask and picks a slug + output folder.
  2. Interviews the user in adaptive batches via AskUserQuestion (2–4 grouped questions per round), up to ~50 questions total.
  3. Traverses the design tree — when an answer materially changes scope or leaves a real ambiguity, branch deeper into that thread before moving on.
  4. Persists every question and answer to a Q&A log in the repo as it goes.
  5. Synthesizes the answers into lite-prd.md in the pasted format (minus Monetization).

Flags

  • --deep: exhaustive branching — pursue every plausible sub-thread until the tree is dry or the ~50-question budget is spent. Default (no flag) is model-judged, biased to fewer: only branch when an answer materially changes scope or leaves a real ambiguity, and prefer finishing over exhausting the budget.

Step 1 — Set up the workspace

  • Derive a short kebab-case <slug> from the feature ask (e.g. "team invites" → team-invites).
  • Create the folder docs/lite-prd/<slug>/ in the repo the skill was invoked in. If it already exists, reuse it and continue an in-progress run rather than clobbering.
  • Create/open the Q&A log at docs/lite-prd/<slug>/qa-log.md. Seed it with the raw ask.

Step 2 — Interview by traversing the design tree

Read references/traversal-protocol.md and follow it exactly. It defines: how to seed the root questions, how to batch with AskUserQuestion, when to branch deeper vs. move on (and how --deep changes that), the ~50-question budget, and the persistence rule (write each round to qa-log.md immediately after the user answers, before asking the next batch).

Every round: ask → read answers → append the round to qa-log.md → decide whether to branch or advance.

Show full SKILL.md (144 more words)Show less

Step 3 — Synthesize the PRD

When the tree is covered (or the budget is spent), read references/prd-template.md and fill every section from the Q&A log. Write the result to docs/lite-prd/<slug>/lite-prd.md.

Rules:

  • Use ONLY what the user actually told you plus low-risk, clearly-labeled inferences. Never invent requirements the interview didn't support.
  • Requirements go in as user stories with - [ ] checkboxes, exactly as the template shows.
  • Omit the Monetization section entirely (per the format).
  • Anything still genuinely unresolved goes under Critical Questions or Clarifications — do not paper over gaps.

Step 4 — Report

Tell the user the two paths written (qa-log.md and lite-prd.md), the question count, and list anything parked under Critical Questions so they know what's still open.

Honesty rule

If the user's answers leave a section unsupported, write "TBD — see Critical Questions" rather than fabricating plausible-sounding content. A confidently-wrong PRD is worse than an honestly-incomplete one.

© ragnar-pwninskjold, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/tech-snacks/skills/lite-prd of ragnar-pwninskjold/tech-snacks.

  • SKILL.md
  • references/prd-template.md
  • references/traversal-protocol.md

Open the folder on GitHubat commit 2d9a73b

Compare with similar skills

Lite Prd 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.

Lite Prd compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lite Prd this skillragnar-pwninskjold/tech-snacks137—~853Automated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Trellis Brainstormanjiemo/SunnyBeach1787 repos~4kAutomated safety check: PassApache-2.0
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
Ralph Tui Create JSONsubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Trellis Brainstorm

    anjiemo/SunnyBeach

    Guides collaborative requirements discovery before implementation.

    178 GitHub starsUsed in 7 repos~4k tokens
    Product & Project ManagementAuto-check passed
  • Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Prd Generator

    jamesrochabrun/skills

    Generate comprehensive Product Requirements Documents (PRDs) for product managers.

    216 GitHub starsUsed in 2 repos~3.8k tokens
    Product & Project ManagementAuto-check passed

More from ragnar-pwninskjold/tech-snacks

  • Prd To UX

    ragnar-pwninskjold/tech-snacks

    A skill your agent uses when translating a PRD, feature spec, or raw product idea into screen-level prompts for web UX generators (Google Stitch, Figma AI, Pencil.dev, Claude Design, v0, or similar).

    137 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Scaffold Claude

    ragnar-pwninskjold/tech-snacks

    A skill your agent uses when the user wants to create, draft, or scaffold a CLAUDE.md (or AGENTS.md) file for their project.

    137 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • UI Cloner

    ragnar-pwninskjold/tech-snacks

    A skill your agent uses when user provides a URL and wants to replicate or clone a website's UI, design, or visual style for their own product.

    137 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Mine Claude Md

    ragnar-pwninskjold/tech-snacks

    Mine recent Claude Code sessions for non-obvious, multi-file CLAUDE.md candidates, adversarially verify them, and propose paste-ready additions.

    137 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed
  • React Refactor Tournament

    ragnar-pwninskjold/tech-snacks

    Review React/Next.js code against the real vercel-react-best-practices skill, backlog the performance findings keyed to actual rule ids + impact tiers, rank the most over-subscribed tiers, then fix…

    137 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Caveman Search

    ragnar-pwninskjold/tech-snacks

    A skill your agent uses when the user wants a terse, opinionated, research-backed answer to a "what tech/tools/stack do I need for X" question, or asks how to approach building something.

    137 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Lite Prd

What does Lite Prd do?

A skill your agent uses when the user hands you a vague or half-formed feature ask and wants it turned into a lightweight PRD, or asks to "write a PRD", "spec this feature", "flesh this out", or…. Lite Prd is an agent skill from ragnar-pwninskjold/tech-snacks. Use when the user hands you a vague or half-formed feature ask and wants it turned into a lightweight PRD, or asks to "write a PRD", "spec this feature", "flesh this out", or invokes /lite-prd.

When should I use Lite Prd?

Lite Prd fits situations like: the user hands you a vague; half-formed feature ask and wants it turned into a lightweight PRD; asks to write a PRD; spec this feature.

How do I install Lite Prd in Claude Code?

Run `npx skills add ragnar-pwninskjold/tech-snacks --skill lite-prd -a claude-code`. Or copy the skill folder (plugins/tech-snacks/skills/lite-prd in ragnar-pwninskjold/tech-snacks) into .claude/skills/lite-prd in your project. Claude Code loads it when a task matches its description.

How do I install Lite Prd in Codex?

Run `npx skills add ragnar-pwninskjold/tech-snacks --skill lite-prd -a codex`. Or copy the skill folder (plugins/tech-snacks/skills/lite-prd in ragnar-pwninskjold/tech-snacks) into .agents/skills/lite-prd in your project. Codex loads it when a task matches its description.

Can I use Lite Prd 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 ragnar-pwninskjold/tech-snacks --skill lite-prd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lite-prd, .gemini/skills/lite-prd, .github/skills/lite-prd and .opencode/skills/lite-prd in your project.

What does Lite Prd need to run?

SKILL.md names no scripts, command-line tools or credentials: Lite Prd is instructions for the agent only.

Does Lite Prd 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 Lite Prd 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 Lite Prd use?

Lite Prd is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lite Prd use?

About 853 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Lite Prd?

Skills that share tags, products or a category with Lite Prd: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lite Prd?

ragnar-pwninskjold (a GitHub user) maintains it in ragnar-pwninskjold/tech-snacks, which has 137 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on August 18, 2026.

Source: ragnar-pwninskjold/tech-snacks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.