Command
Estimates the ongoing Operating Costs of the chosen architecture for various usage scenarios. The goal is realistic cost planning that feeds back into the financial plan – no surprises after launch.
Command
Designs the Data Model with entities and relationships as well as the API design with interface specification. The result is DATAMODEL.md and APISPEC.md as the binding foundation for implementation.
Command
Designs the CI/CD pipeline with stages, branch strategy and rollback concept.
Command
Plans hosting platform, deployment model, environments and CDN strategy.
Command
Defines logging, metrics, alerting and error tracking.
Command
Defines test levels, test tools, coverage targets and critical test paths.
Command
Plans infrastructure, CI/CD pipeline, monitoring and test strategy. Each area is its own sub-skill.
Command
Defines input validation, rate limiting, CORS and security headers.
Command
Defines the authentication and authorization concept including session management.
Command
Creates a concrete checklist that every feature in phase 5 must fulfill.
Command
Defines encryption (transit/rest), secrets management and backup security.
Command
Analyzes the system according to the STRIDE model and identifies threats with countermeasures.
Command
Creates the complete security architecture: threat model, auth concept, data security, API security and developer checklist. Each area is its own sub-skill.
Command
Defines WCAG target, contrast requirements, keyboard navigation, screen reader requirements and testing methods.
Command
Defines the color strategy for dark mode with semantic colors and toggle mechanism.
Command
Creates the navigation structure, sitemap and identifies critical flows.
Command
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
Command
Develops the complete UX concept: navigation, wireframes, dark mode and accessibility. Each area is its own sub-skill.
Command
Breaks down the features from FEATURES.md into actionable tasks, builds the prioritized backlog, and defines milestones and release planning. The result is BACKLOG.md and PROJECTPLAN.md as the steering foundation for the entire implementation.
Command
Creates the foundational project documentation: a meaningful README, a contributing guide, and documentation of the project structure. The result is a documentation base that quickly onboards new developers and bindingly establishes standards.
Command
Sets up the repository, CI/CD pipeline and local development environment. The result is a working development infrastructure in which the team can immediately start with /p5-implement.
Command
Plans the current sprint: pulls matching stories from the backlog, defines the sprint goal, identifies risks, and creates the sprint document. Called repeatedly at the start of each new sprint.
Command
Tests an implemented feature against its requirements from a user perspective: are all acceptance criteria met? Are edge cases handled correctly? The result is test findings that determine whether the feature counts as "Done".
Command
Systematically analyzes a found bug, identifies the root cause and fixes it with an accompanying regression test. Goal: the bug is fixed, secured by a test, and cannot be silently reintroduced.
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: