Command Claude Code
Runs systematic functional tests at the system level. Each test level is a separate sub-skill.
Command Claude Code
Runs systematic functional tests at the system level. Each test level is a separate sub-skill.
Command Claude Code
Actively tests authentication: brute-force protection, token predictability, session invalidation, JWT confusion.
Command Claude Code
Tests IDOR, horizontal/vertical privilege escalation, and unprotected endpoints.
Command Claude Code
Tests SQL injection, XSS, and command injection on input fields and API parameters.
Command Claude Code
Tests manipulation of business logic: prices, quantities, race conditions, flow bypasses.
Command Claude Code
Collects publicly available information: tech fingerprinting, exposed endpoints, debug remnants.
Command Claude Code
Conducts an active attack simulation. Each attack phase is a separate sub-skill.
Command Claude Code
Executes the deployment to the target environment and then verifies with smoke tests that the system is running correctly. Only when the smoke tests pass is the deployment considered successful.
Command Claude Code
Launches the go-to-market activities and sets up KPI tracking. The result is active marketing measures and a working tracking setup that delivers meaningful data from day one.
Command Claude Code
Sets up production monitoring completely, configures alerting rules, and tests the rollback plan. The goal is a system that reports problems early and where a rollback works smoothly in an emergency.
Command Claude Code
Prepares the deployment: checks all environments, prepares database migrations, verifies configurations, and ensures nothing has been overlooked. Only after this checklist is complete will /p7-deploy be executed.
Command Claude Code
Creates all user-facing documents for the launch: release notes, user guide or onboarding materials, and the legally required mandatory documents (privacy policy, legal notice). These documents must be available before go-live.
Command Claude Code
Evaluates the KPIs from ongoing operations, compares them with the plans from FINANCIALPLAN.md, and derives optimisation measures for the business model. Called regularly (recommended: monthly) or on an ad-hoc basis.
Command Claude Code
Evaluates user feedback and operational insights, maintains the backlog, and initiates the next iteration. This is the link between ongoing operations and the next development round – the engine of the evolution loop.
Command Claude Code
Analyses production errors and performance issues, evaluates incidents, and initiates countermeasures. Called reactively for specific incidents or proactively for regular operational reviews.
Command Claude Code
Keeps the security of the running system current: regular dependency updates, security scans, checking for new CVEs, and periodic re-tests of critical areas. Security is not a one-time task – it must be continuously maintained.
Command Claude Code
Analyze the last session and extract instinct proposals.
Command Claude Code
Initializes a new project with directory structure, project-specific CLAUDE.md, and Git repository.
Command Claude Code
Makes a "cut" after a release: project state is documented as given, HANDOVER is archived and summarized, docs are split into Frozen/Active.
Command Claude Code
This command updates an existing roadmap based on new findings, completed milestones, changed priorities, or new decisions. Each revision is versioned and timestamped with date + time.
Command Claude Code
This command creates a first roadmap based on an existing rough concept. The roadmap structures epics, milestones, and dependencies either time-based (quarters/months) or phase-based (MVP, Phase 1, Phase 2...) – selectable depending on the project character.
Command Claude Code
Generic CCPR agents are tech-stack-agnostic all-rounders. Once the stack is known, this command writes project-local specialized copies under .claude/agents/ (which take precedence over /.claude/agents/ via Claude Code's name resolution) and injects a Project Tech Context block carrying stack-specific correctness…
Command Claude Code
Interactive prerequisite check + Knockout check + Indicator score that determines whether a project runs in Lean-Track (prototype/PoC/spike, 4 skills) or Full-Track (P0–P8, 109 skills).
Command Claude Code
This command creates detailed user stories – either derived from an existing epic, roadmap, or concept, or standalone from a free description. Each story contains acceptance criteria, priority, dependencies, and a definition of done.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: