codespring

CodeSpring CLI

Manage project planning: workspaces, projects, tasks, PRDs, and mindmaps.

Prerequisites

• CLI installed: npm i -g @codespring-app/cli or use npx @codespring-app/cli
• Authenticated: Run codespring auth status to check. Login with codespring auth login.
• Project linked: Check for .codespring/config.json or run codespring init.

Quick Start

# 1. Check auth
codespring auth status
 
# 2. Link project (interactive — picks workspace → project → writes config)
codespring init
 
# 3. Start working
codespring tasks --status todo

Core Commands

Note: Task IDs can be UUIDs or row numbers (e.g., task start 1 picks the first task from the list).

Output

All commands default to markdown in terminals, JSON when piped. Add --json to force JSON, --pretty for formatted JSON, --md for markdown.

Agentic Task Workflow

Syncing Codebase Analysis

After analyzing a codebase, sync findings:

Generating PRDs

The CLI reads and syncs PRDs; it does not yet generate them. PRD generation and attaching PRD nodes to the canvas is a direct API call the CodeSpring app uses — see prd-management.md and mindmap-structure.md. The cs-build-create-prd skill wraps this end-to-end.

Scripts — run the checks, don't eyeball them

A check is a script; a judgement is prose. Anything that must give the same answer every run lives in scripts/, read-only, writing nothing to the project or the repo:

check-map.mjs settles the core-feature count, duplicate titles, sub-features flattened to top level, missing notes, duplicate PRDs and unlinked tasks; exit 1 = a real failure, 2 = warnings only. Whether the map is good — sidebar-level features, verbs for sub-features, one-sentence card descriptions — stays a judgement and stays in prose. cs-build-audit-codebase/scripts/check-repo.sh does the same for the git/delivery reality.

Detailed References

• project-state.md — Start here. State detection so any skill can be entered from anywhere; the five questions that decide whether code is worth building on; the Understand → Plan → Build stages and the seam between them; the map-quality caveat and the two-projects case; the quick health smell test
• auditing-and-fixing.md — The audit → verdict → map → tasks pipeline; where audit errors actually come from (the orchestrator's own summarising); the moving-target/git reality; why the map shows the target; the rebuild-vs-fix decision table and the has-users gate; the defect categories worth hunting; scope discipline (problems / could-add-later / not-worth-adding) and where future ideas live; plain-language rules; idempotency + verification; FERB edge cases
• commands.md — Full CLI reference with all flags
• task-workflow.md — Agentic task execution patterns
• analyze-codebase.md — Codebase analysis checklist (stack detection + deep feature/backend/frontend passes; choosing the smallest core-feature set)
• mindmap-structure.md — Mindmap data formats and node types (incl. PRD bridge nodes)
• prd-management.md — PRD read/sync + generate/attach/dedupe
• pitfalls.md — Failure modes & guardrails (not checking what exists, wrong-project, flattening, duplicate PRDs, features --replace appending, no project delete/move)

Related skills

This codespring skill is the shared knowledge base (how CodeSpring works + the CLI). The task-specific skills build on it. Every one of them detects the project's real state on entry (project-state.md), so it does not matter which the user invokes:

• cs-build-getting-started — connect, report where the project actually is, and name the single next step. Routes on two questions: is there code, and does it do the job (the five questions in project-state.md — never "do we trust it").
• cs-build-plan-app — no code yet, just an idea or a call recording. Interviews or mines the source, picks the platform on capability, proves the one hard part, cuts to a sellable v1, then writes the map and notes.
• cs-build-audit-codebase — diagnose a codebase that isn't doing its job (run it, parallel specialists, git/CI audit), write a plain-English FINDINGS.md, and give a rebuild-or-fix-in-place verdict.
• cs-build-import-codebase — map a repo into CodeSpring. With an audit it builds the corrected target map and findings-derived tasks; without one it documents what exists. Owns the map-quality ladder and the node model.
• cs-build-ui-mockup — a throwaway clickable mockup and style guide from the notes, reviewed with the client, corrections fed back into the plan. Before the PRDs, for anything with a user interface.
• cs-build-create-prd — generate a Frontend/Backend PRD for a chosen feature (the single source of truth for PRD creation).
• cs-build-create-tasks — turn a feature's PRDs into a numbered, parallel-safe task list.
• cs-build-handoff — turn the finished plan into the pack a paying client actually receives.
• cs-build-feature — interactive build orchestrator (readiness checks → up to 5 sub-agents → break-risk guards).
• cs-build-resync-codebase — keep CodeSpring in sync with the built code (read-only on code). This is what makes a target map describe reality again once the tasks are done.

See references/codespring-docs.md for guiding users through web-app-only steps, and claude-templates/ (repo root) for per-platform CLAUDE.md starters.