imagine

Solid

One-shot draft PRD sketch from a fuzzy scenario. Writes a single artifact to .claude/specs/<slug>/spec.md — a path that is gitignored by default (`.gitignore:51`), so the spec never enters git history. Includes a mermaid diagram. Output is purpose-built as input for `/ship-spec --plan .claude/specs/<slug>/spec.md`, which bypasses /prd's clarifying questions when a plan is provided. No clarifying questions in /imagine itself — generate directly from the <scenario> argument. TRIGGER when: /imagine invoked, or asked to "sketch a spec", "imagine a feature", "draft a quick PRD", "what if we built X".

AI & Automation 38 stars 3 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Imagine One-shot generator that turns a fuzzy scenario into a draft PRD sketch under `.claude/specs/<slug>/spec.md`. The output is **scratch-input for `/ship-spec`** — gitignored by default, never committed, designed to be edited locally and then passed via `/ship-spec --plan <path>` to the existing formalization pipeline. ## When to use - The user has an idea but the shape is still fuzzy — they don't want to sit through `/prd`'s 3–5 lettered Q&A yet. - The user wants a tangible artifact they can edit before formalizing. - Quick what-if exploration: "imagine a /summarize command", "what if we added X". ## When NOT to use - **`/prd`** — when the feature is already well-defined and ready for a structured PRD with numbered FRs and acceptance criteria. `/imagine` outputs a sketch, not a PRD. - **`/ship-spec`** — when ready for the full pipeline (PRD → critics → issue → branch → draft PR). `/imagine` produces input for `/ship-spec`; it does not replace it. - **`/interview`** — when the goal is to narrow scope on a *known* task. `/imagine` is for *generating* a new task shape from a scenario. ## The job 1. Receive `<scenario>` as a free-text argument. 2. Derive a slug from the scenario. 3. One-shot generate the spec body (no clarifying questions). 4. Write `.claude/specs/<slug>/spec.md`. 5. Print the path and the next-step command. 6. Append a Memory Protocol entry. ## Step 1 — Parse `<scenario>` and derive slug Arguments received: `$ARGUMENTS` The slug rule is **the sa...

Details

Author
mifunedev
Repository
mifunedev/openharness
Created
5 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category