cc-skill:product-spec-generator

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

Generates a complete product or feature specification in Jay's standard format. The spec includes the core insight, architecture diagram, database schema, tool assignments, detailed workflows, a 30-day rollout plan, success metrics, and a hand-off prompt ready for Claude Code to build from.

who it is for

Founders and product leaders who need to move quickly from idea to buildable spec without waffling on architecture or scope.

when it fires

When someone asks to 'spec out', 'design', 'architect', 'write a spec', 'create a PRD', or 'build me a plan for' a new product, feature, or system.

say something like

"Spec out a customer feedback loop that feeds into our product roadmap"
"Design a system to handle our Stripe billing reconciliation"
"Write a spec for an internal tool to track project status across the team"

what you might get back

The output is a structured document with sections for core insight, ASCII architecture diagram, Postgres schema, tool map, numbered workflows with triggers and costs, a 30-day rollout timeline, success metrics at 30/60/90 days, a 'what not to do' list, and a Claude Code hand-off prompt with explicit stop points. For example: a billing sync system spec might show which Stripe webhooks trigger reconciliation, how disputes land in Postgres, which existing tools handle notifications, and the exact sequence Claude Code should build first (validation before scale).

how to know it worked

You will know it fired correctly because the output includes all 10 sections in order, references Jay's stack defaults, limits v1 code to under 800 lines, and ends with a numbered build sequence for Claude Code with at least one STOP point.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/product-spec-generator/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when Jay asks to "spec out", "design", "architect", or "build me a plan for" a new product, feature, system, or workflow. Generates specs in his standard format: insight → architecture diagram → schema → workflows → rollout sequence →

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/product-spec-generator/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when Jay asks to \"spec out\", \"design\", \"architect\", or \"build me a plan for\" a new product, feature, system, or workflow. Generates specs in his standard format: insight → architecture diagram → schema → workflows → rollout sequence → don't-do list → Claude Code hand-off prompt. Triggers also on \"write a spec\", \"design doc\", \"PRD\", or \"technical spec\"."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/product-spec-generator/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.