Skill UI

CCPM orchestrates software delivery from PRD through epics and GitHub issues into parallel agent execution, covering planning, decomposition, syncing, workstart, and status checks with mandated script-based reporting.

This advanced prompt simulates a Senior Project Manager and DevOps specialist. It takes comprehensive feature artifacts (PRD, technical breakdowns, testing plans) and generates a structured, automated GitHub project plan. It enforces Agile best practices (Epic > Feature > Story > Enabler > Task) and includes templates for issue creation, dependency management, risk assessment, and Definition of Done, ensuring robust project tracking within GitHub.

A comprehensive guide to creating production-grade Product Requirements Documents (PRDs). This skill helps bridge the gap between vague business concepts and concrete technical specifications for modern software systems and AI features. It enforces a structured workflow, ensuring all necessary components—from user stories and success KPIs to technical architecture and risk analysis—are defined.

This skill generates a comprehensive and structured test strategy document. Given a feature specification, PRD, or system description, it systematically outlines the test scope, performs a detailed risk assessment, defines necessary test types (Unit, E2E, Performance, Security), and provides a prioritized, actionable test case outline to ensure robust quality assurance before release.

This tool evaluates how thoroughly a feature implementation meets product requirements (PRDs) or specifications. It scores acceptance criteria case-by-case, independently grading both the code implementation and the associated test coverage (unit and E2E). Ideal for benchmarking multiple development efforts, auditing adherence to specifications, or determining if a feature is 100% complete and compliant with the ground truth PRD.

This skill guides the structured development process for implementing new features or fixes based on Product Requirement Documents (PRDs) or predefined issues. It emphasizes best practices, including Test-Driven Development (TDD), regular type-checking, running comprehensive test suites, and completing the cycle with a formal review process.

Orchestrates bootstrapping a working MVP from a design or spec document: ingest the SDD/PRD, plan thin vertical slices, scaffold the first end-to-end slice, then drive a generator-evaluator build loop with review gates and gated feat commits.

This robust pipeline guides development teams through a rigorous, five-phase planning process *before* writing any code. It systematically analyzes PRDs, design specifications (UX, accessibility), and existing architecture to produce a comprehensive implementation plan. Key outputs include Architecture Decision Records (ADRs), detailed task breakdowns, and verification strategies, ensuring all technical and design decisions are documented and scoped.

Captures a short user pitch, then drafts a product overview (PRD.md) and technical design (ARCHITECTURE.md) for a third-party .ppmplugin native control. Walks through every operation's iOS and Android implementation strategy with opinionated recommendations and iterates with the user until approval. The resulting docs serve as the source of truth for downstream code-generation skills.

This skill transforms vague project ideas into eight structured planning documents for new software projects. It acts as persistent memory, prioritizing user instructions over AI assumptions. It generates PRD, TechSpec, Design, and other files sequentially, ensuring clear architecture and design direction before coding begins. Ideal for starting fresh projects from scratch.

Freezes PRD, technical design, and acceptance criteria before medium-to-large Codex work, then coordinates multiple agents with explicit file ownership and judges delivery from diffs, tests, and evidence-backed acceptance.