Menu
Create a PRD for a new project. Research, scope, write — no code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Execute a PRD end-to-end. Branch, implement everything in the PRD, commit. Autonomous — the PRD is the spec.
Curate the LS graph by creating/updating nodes, dimensions, and edges with strict quality and dedupe checks.
Create and maintain LS Hub guides via MCP guide tools with immutable system-guide protection.
Triage new source material into normalized node records, dimensions, and follow-up extraction work.
Research topics in Latent Space Hub with retrieval-first workflow: search nodes, drill into chunk content, then load full records.
Merge feature branch, update docs, clean up. Run after /dev completes.
| name | plan |
| description | Create a PRD for a new project. Research, scope, write — no code. |
Creates a PRD (Product Requirements Document) for a project. PRDs go in docs/development/. No code changes allowed in plan mode.
Read these files:
CLAUDE.md — project contextdocs/development/backlog/backlog.json — existing queuedocs/development/process.md — workflowAsk clarifying questions if needed. Understand:
Read relevant source files to understand:
Create docs/development/prd-XX-[name].md:
# PRD XX: [Title]
## Background
[Why this matters, what's broken/missing]
## Plan
[Numbered steps]
## Part N: [Section]
### File: path/to/file
[Exact changes — what to add/remove/modify]
## Done =
- [ ] [Acceptance criteria]
Add the project to docs/development/backlog/backlog.json:
queue array (position based on priority)status: "ready"prd path