Create a PRD in CodeSpring

A PRD gives CodeSpring a full, accurate understanding of a feature so new features build on what exists instead of duplicating backend, re-creating a shared API route, or reinventing the design system. This skill makes the Frontend and/or Backend PRD for a chosen feature, grounded in the real code.

This is the single source of truth for how PRDs get made — other skills (e.g. cs-import-codebase) call this rather than re-implementing it.

Shared knowledge is in the codespring skill's references: references/analyze-codebase.md, references/mindmap-structure.md, references/prd-management.md, references/pitfalls.md, references/codespring-docs.md.

0. Connect first

codespring auth status (login if needed) + codespring status. Use the projectId from the local .codespring/config.json; print it. If the codebase isn't in CodeSpring yet, run cs-import-codebase first. This skill READS code and WRITES only to CodeSpring — never modify the codebase.

1. Ask what to generate (interactive)

Show the user their core features (from codespring features / the mindmap node-features items), then ask:

1. Which feature? (one, several, or all)
2. Frontend, Backend, or Both? Wait for their choice unless they already said.

2. Deep-dive the real code

Read the actual code for the feature (don't guess). Pull in the depth from analyze-codebase.md §8–9. Cover: