rptc

Verify and ship with quality gates

Configure RPTC workflow in project CLAUDE.md - sync with current version

Team-based feature development with parallel research, planning, implementation, and review agents

Research → Plan → TDD → Verify in one seamless flow

Team-based bug fixing with parallel reproduction, root cause analysis, fix, and review agents

Implementation planning specialist. Maps file changes, designs TDD-first test strategies, identifies dependencies and risks. For medium-to-complex features requiring structured TDD.

Code review specialist with confidence-based reporting. REPORT ONLY - does not make changes. Identifies KISS/YAGNI violations, complexity issues. Main context handles fixes.

Documentation review specialist with confidence-based reporting. REPORT ONLY - does not make changes. Identifies stale docs, missing updates, breaking changes. Main context handles fixes.

Unified research specialist for codebase exploration and web research. Mode A uses 4-phase code-explorer methodology. Mode B consults 20+ sources with cross-verification. Mode C combines both with gap analysis.

Unified quality reviewer combining code review, security analysis, and documentation checks. REPORT ONLY - does not make changes. Provides real-time feedback to implementation agents in team workflows. Covers KISS/YAGNI violations, OWASP Top 10, and documentation sync.

Agent Teams execution mode for RPTC. Invoke explicitly when coordinating multiple independent work streams across parallel agent sessions — batch features, parallel bug fixes, or sprint items that don't share files. Orchestrates team creation with RPTC-compliant spawn prompts, file ownership boundaries, approval flow, and completion integration. For team-based single-feature or single-bug workflows, prefer `/rptc:feat-team` or `/rptc:fix-team` — this skill targets multi-stream batch work.

Planning methodology for the RPTC architect-agent. Covers incremental sub-agent delegation, implementation constraints generation (5 categories), 6-phase planning methodology (context analysis, test strategy, implementation steps, dependencies/risk, self-critique, output), context management strategy, quality standards, best practices, and anti-patterns. Produces TDD-ready implementation plans.

Use during planning phases to explore user intent, requirements, and design through structured dialogue before implementation.

Code review methodology for the RPTC code-review agent. Covers hierarchical review framework (4 tiers), over-engineering checklist, integration completeness check, behavioral testing checklist, assertion quality checklist, false positive guidance, confidence scoring (>=80 threshold), domain-specific checks, and structured output format. Report-only mode.

Shared principles for RPTC agents. Loaded at session start by all agents. Contains Surgical Coding, Simplicity Directives, Pattern Reuse (Rule of Three), SOP references, and evidence-based rationale. Must be read before any work begins.