Build a feature from its CodeSpring plan

A guided, interactive build. Do NOT jump straight to writing code — walk the user through readiness first, then build in a controlled way. This skill both reads the plan and (in the build phase) edits the codebase, so be deliberate.

Uses: codespring skill references (task-workflow.md, prd-management.md, pitfalls.md, codespring-docs.md), and the sibling skills cs-build-create-prd and cs-build-create-tasks.

0. Connect first

codespring auth status + codespring status (LOCAL project; print it).

1. Interview — what are we building?

Ask the user what feature they want to build. Then read what CodeSpring has and reflect it back in 3 simple bullet points: "Here's what I think we're building — confirm or correct." Keep it plain-language.

2. Readiness check — is there enough context?

For the target feature, verify:

• A how-it-works note exists and is substantive.
• Frontend and Backend PRDs exist (codespring prds / codespring prd <id>).
• The Backend PRD actually covers the shared systems (routes, data model, auth/RLS, jobs/cron, storage, payments/credits, env vars) and a dependency map.