Use for rankingdepadel.club SDD planning interviews, "grill me" prompts, plan pressure-tests, unresolved product or architecture decisions, and pre-implementation planning that should end in a decision-complete proposed plan.
Use for rankingdepadel.club implementation handoffs, changelog and issue/spec reconciliation, commits, pushes, release consolidation, and ending a development cycle.
Use for rankingdepadel.club product/code work, active SDD specs, Codex planning, repository constraints, and deciding whether review or audit checkpoints apply.
Use for rankingdepadel.club governance edits, instruction version/date alignment, markdown rules, governance validation, changelog wording, and maintaining progressive disclosure between router docs and skills.
Audit Django views for project governance, security, reuse, and maintainability issues.
Review governance, skills, scripts, and repository files for context bloat, token-heavy workflows, and progressive-disclosure gaps. Use by default for conversations that are likely to be long or broad, and when the user asks to keep work under a context budget, reduce token consumption, or audit files for context efficiency.
Audit governance markdown and workflow skills for duplication, unclear ownership, coordination gaps, prose-only rules, and low-value SDD artifact overhead; export a reviewable governance audit report with prioritized findings and a consolidation-first rewrite plan.
Create persistent PRDs for complex rankingdepadel.club work that should later be split into approved implementation phases. Use when a requested feature, refactor, or process change is too large for one SDD spec, needs phased delivery, or should preserve product decisions before phase planning.