菜单
Execute a PRD end-to-end. Branch, implement everything in the PRD, commit. Autonomous — the PRD is the spec.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | dev |
| description | Execute a PRD end-to-end. Branch, implement everything in the PRD, commit. Autonomous — the PRD is the spec. |
Latent Space Hub: A Next.js 15 knowledge base for the Latent Space community. Turso (cloud SQLite) backend, deployed on Vercel. NOT a demo — this is the product.
Read these files in order:
CLAUDE.md — project overview, architecture, key constraintsdocs/development/backlog/backlog.json — the work queueThen confirm:
"Loaded context. Working on: [PRD title]. Creating branch: feature/[name]."
ALWAYS create a feature branch. Never work on main.
git status --porcelain
git checkout main && git pull origin main
git checkout -b feature/[project-id]
The PRD IS the spec. It tells you exactly what to change, file by file. Read it completely before writing any code.
Work through the PRD systematically. The PRD has been scoped — don't ask for confirmation on each step. Just do the work.
Rules:
npm run type-check after changes to catch type errorsAfter all changes:
npm run type-check # Must pass
npm run build 2>&1 | head -50 # Check for build errors
If the app has UI changes, note them for manual testing but don't block on it.
Update the PRD — add completion section:
---
## COMPLETED
**Date:** [Today's date]
**What was delivered:** [Brief summary of all changes]
Update docs/development/backlog/backlog.json — mark tasks as done, update project status.
Commit everything:
git add .
git commit -m "feat: [concise description]
- [Key change 1]
- [Key change 2]
- [Key change 3]
Generated with Claude Code"
Then report:
"Done. Branch: feature/[name]. Changes: [summary] Type-check: [pass/fail] Ready for review and merge."
Create a PRD for a new project. Research, scope, write — no code.
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.