jonase47

jonase47/ccpr

Instructions file

Claude Code instructions for jonase47/ccpr, covering global preferences (local, interactive mode), language & communication, personal context, infrastructure and code standards.

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

Agent

Business Analyst for Business Models, financial planning, market analysis, pricing strategies, and economic viability assessment. Used PROACTIVELY for questions about business cases, cost calculations, Revenue Forecasts, break-even analyses, competitive analyses, go-to-market strategies, KPIs, grants, and financing…

jonase47/ccpr

Agent

Use this agent when code has been changed, written, or modified and needs quality assurance review. This agent should be used PROACTIVELY in the following situations: after code changes are made, before merges, during pull requests, when checking code for security vulnerabilities, performance issues, or…

jonase47/ccpr

Agent

Use this agent when encountering bugs, error messages, unexpected behavior, failing tests, performance problems, crashes, or any situation requiring systematic troubleshooting and root-cause analysis. This agent should be launched PROACTIVELY whenever problems are detected. Examples: Example 1: Context: A test suite…

jonase47/ccpr

Agent

DevOps and infrastructure specialist for CI/CD pipelines, deployment, containers, cloud infrastructure, monitoring, and automation. Used PROACTIVELY for questions about deployment strategies, Docker, Kubernetes, GitHub Actions, hosting, domain management, SSL, monitoring, and infrastructure-as-code.

jonase47/ccpr

Agent

Use this agent when the user needs help with product concepts, business cases, user journeys, target audience analysis, feature prioritization, market positioning, or MVP definition. This agent should be used PROACTIVELY whenever product conception topics arise.\n\nExamples:\n\n- User: "I have an idea for an app that…

jonase47/ccpr

Agent

Use this agent when you need to actively test applications, APIs, infrastructure, or code for exploitable vulnerabilities. This agent thinks like an attacker and finds entry points before real attackers do. It complements the security-master agent through practical attack simulation. This agent should be used…

jonase47/ccpr

Agent

Phase-aware orchestrator and entry point for every project. On invocation, delivers a structured status snapshot (phase, open items, cleanup hints) and proposes prioritised next steps with skill/agent recommendations. Disambiguates unclear requests and hands off with a bundled context. Used at session start, for "what…

jonase47/ccpr

Agent

Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…

jonase47/ccpr

Agent

Use this agent when the user needs help with test strategy, test planning, test case design, exploratory testing, test automation, acceptance testing, regression testing, test coverage analysis, quality metrics, bug reporting, or any quality assurance related tasks. This agent should be used PROACTIVELY in the…

jonase47/ccpr

Agent

Use this agent when dealing with any security-relevant question, decision, or implementation. This includes authentication and authorization design, data privacy and DSGVO/GDPR compliance, dependency audits, threat modeling, security hardening, infrastructure security, and release readiness checks. This agent MUST be…

jonase47/ccpr

Agent

Use this agent when the user needs programming tasks executed, including feature implementation, refactoring, bug fixing, code reviews, or any code-related work. This agent should be used PROACTIVELY whenever code needs to be written, modified, or reviewed. It strictly follows Test-Driven Development…

jonase47/ccpr

Agent

Use this agent when the user needs help with system architecture decisions, technology selection, data modeling, API/interface design, infrastructure planning, security architecture, scalability considerations, or technical feasibility analysis. This agent should be used PROACTIVELY whenever architectural topics…

jonase47/ccpr

Agent

Use this agent when the user needs technical documentation, READMEs, API documentation, user guides, onboarding guides, changelogs, release notes, architecture documentation, runbooks, or any form of written technical communication. This agent should be used PROACTIVELY whenever documentation-related tasks arise.…

jonase47/ccpr

Agent

UX Design specialist for user-centered design, UI concepts, usability, Accessibility, and information architecture. Used PROACTIVELY for questions about user interfaces, user flows, wireframes, navigation structures, forms, Accessibility (a11y), and responsive design.

jonase47/ccpr

Agent

Result consolidator: Reads agent results from files, summarizes them into a compact summary. Used after parallel agent runs when multiple result files need to be merged.

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.