jonase47/ccpr

jonase47/ccpr

Command

Quality gates between phases — single-purpose decision points. Main gates (P0–P7) plus sub-gates for the dual-approval gates P6 (QA + Security) and P7 (Tech + Business).

jonase47/ccpr

Command

Meta-commands for capturing session insight back into the system.

jonase47/ccpr

Command

All P0–P8 phase commands grouped per phase. Lead commands appear first, then sub-skills in execution sequence where applicable.

jonase47/ccpr

Command

Entry-point and cross-cutting commands. /track-decision runs first; the others compose Lean-Track / Full-Track / consistency checks.

jonase47/ccpr

Command

Cross-cutting commands that operate outside the phase flow.

jonase47/ccpr

Command

Checks phase documents against the code they describe, not against other documents. Where /cross-check compares Markdown to Markdown, /anchor compares a document's declared anchorcommit to the repository's actual history — the two-stage check design of docs/adr/ADR-0009-anchored-state-verification.md (both addenda).

jonase47/ccpr

Command

Runs a one-shot hygiene pass on a project's docs to keep them lean and machine-readable: HANDOVER inbox triage and size cap enforcement plus the four existing lint scripts (memory-lint.sh, phase-docs-lint.sh, doc-volume-check.sh, manual-lint.sh) bundled into one consolidated drift report. Use this between phases…

jonase47/ccpr

Command

Creates or updates docs/CONSTITUTION.md — the project Constitution with three sections (Inviolable / Default / Aspirational). Read as a mandatory input by all Full-Track Gates and used as a consistency check for every ADR and implementation decision.

jonase47/ccpr

Command

Reads phase indexes and selected detail files, checks inconsistencies between phases (architecture ↔ implementation, features ↔ stories, threats ↔ mitigations, etc.).

jonase47/ccpr

Command

This command analyzes an open decision question, automatically determines which perspectives are relevant, assembles the appropriate analysis agents, and develops a structured decision basis (Decision Basis) – without making the decision itself. That is the PO's responsibility.

jonase47/ccpr

Command

This command creates one or more epics – either derived from an existing concept or roadmap, or standalone from a free description. An epic can already contain rough associated user stories or be created as a pure high-level shell – this is selectable per call.

jonase47/ccpr

Command

Checks whether all criteria of the Discovery phase have been met and prepares the Go/No-Go Decision. No argument – this gate always checks the complete checklist.

jonase47/ccpr

Command

Checks whether all results of the conception phase are complete and robust, and prepares the transition to the validation phase. No argument – this gate always checks the complete checklist.

jonase47/ccpr

Command

Checks whether all critical Assumptions have been validated and a well-founded Go/No-Go/Pivot Decision can be made. This is the most important gate in the model – here it is decided whether to invest in the cost- and time-intensive architecture and implementation phase. No argument – this gate always checks the…

jonase47/ccpr

Command

Checks whether all architecture and design decisions are completely documented and robust before transitioning into the planning and implementation phase. No argument – this gate always checks the complete checklist.

jonase47/ccpr

Command

Checks whether all organizational and technical prerequisites are met to begin implementation. This is a readiness gate – all participants must know what to do first. No argument – this gate always checks the complete checklist.

jonase47/ccpr

Command

Checks at the end of each sprint whether all tasks meet quality standards and the sprint can be considered successfully completed. Called repeatedly after each sprint. No argument – this gate always checks the complete current sprint status.

jonase47/ccpr

Command

Evaluates all QA-relevant points of the Gate-P6 checklist and grants QA approval.

jonase47/ccpr

Command

Evaluates all security-relevant points of the Gate-P6 checklist and grants Security approval.

jonase47/ccpr

Command

Checks whether the system is ready for launch. Both QA and Security must explicitly grant approval. No go-live without dual approval.

jonase47/ccpr

Command

Checks business readiness: documentation, GTM, KPIs, legal mandatory documents.

jonase47/ccpr

Command

Checks technical go-live readiness: deployment, monitoring, rollback, smoke tests.

jonase47/ccpr

Command

Checks whether the system is fully ready for production operation. Last gate before the official go-live status.

jonase47/ccpr

Command

Invokes the project-guide agent as the entry point for the current project: structured status snapshot, prioritised next steps with skill/agent recommendation, and disambiguation for unclear requests.