AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
Developer role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.
Development standards and best practices. Use when development standards guidance is required.
Azure DevOps Sprint 254-262 new features and enhancements (2025)
Expand seeds and escape convergent ideation. Use when you have the start of an idea and want to grow it, when brainstorming produces the same ideas every time, or when you need to explore possibility space.
R-DOS development process. Use when planning features, creating documentation, tracking work with beads, or understanding the documentation system.
Use when activating visual showcase modes (supersaiyan, kamehameha, over9000) for UI or interaction design - provides mode-specific enhancement checklists.
Write user stories with P1/P2/P3 priorities, Given/When/Then acceptance scenarios, and independent tests. Use when writing user stories, feature specifications, acceptance criteria, or when you see "user story", "acceptance scenario", "Given When Then", "priority", "P1", "P2", or "P3".
Manages MPEP index lifecycle including downloads, building, maintenance, and optimization.
Use when you have a complete feature spec and need to plan implementation - analyzes task dependencies, groups into sequential/parallel phases, validates task quality (no XL tasks, explicit files), and calculates parallelization time savings
Execute Sprint with inspect-and-adapt cycles. Use when implementing subtasks, adapting plans based on progress, or managing sprint execution.
Expert guidance for setting up and organizing research software projects following Sam Abbott's established patterns for R packages, Julia packages, and research projects
Manage TODO files as persistent working memory for complex patterns. Track design decisions, implementation progress, and context across sessions. Use when starting complex patterns or resuming multi-session development work.
Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Expert in the latest Go ecosystem including generics, workspaces, and cutting-edge frameworks. Use PROACTIVELY for Go development, architecture design, or performance optimization.
Multi-agent coordination for parallel plan execution with the coordinate and coord_output tools.
Professional software implementation skill for building features, components, and systems through multi-phase TDD development and incremental delivery.
Validate completed implementation against plan tasks and acceptance criteria. Use when: (1) Implementation is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code.
This skill provides screenplay page count and runtime estimation formulas. Covers the page-to-screen rule (1 page = 1 minute), genre adjustments, target lengths for features vs shorts, and element-based calculations. Use when: estimating screenplay length, calculating runtime, tracking page count, or validating target length for submission requirements.
Complete backlog implementation in feature-driven development. Read backlog requirements, reference implemented features, design approach, implement code, and document. Use when implementing features, changes, bug fixes, or improvements.
Find the gaps in your plan before your stakeholders do. Pressure tests plans, strategies, and communications. Domain-smart advisor, not nitpicker.
