Break vague requirements into precise business rules (BR-*), constraints (C-*), and formulas (F-*) for code generation. Orchestrates extraction of BR-*, C-*, F-* from REQ-*. Use after requirement-extraction to enable autogeneration.
Use when you have architecture documentation from system-archaeologist and need critical assessment, refactoring recommendations, or improvement prioritization - routes to appropriate architect specialist skills
This skill should be used when the user asks to "implement", "build", "create", "add feature", "develop", "design", "architect", "plan", "structure", "refactor", "improve", "optimize", "fix", "solve", "handle", "choose between", "which approach", or discusses implementation strategies. Apply this philosophy to ALL development work as a cornerstone principle.
Shared standards for decision checkpoints, manifest shape, revisioning, reproducibility, and privacy across the process mining skill suite.
Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards.
Apply Ralph Wiggum Method patterns for decomposing tasks into atomic user stories
Track complex, multi-session work with dependency graphs using beads issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.
Spec-driven development methodology that transforms feature requests into structured documentation before coding. Use when users want to (1) plan a new software project or feature, (2) create requirements/design/tasks documentation, (3) follow a structured development workflow, (4) break down complex features into trackable tasks. Triggers include phrases like "let's plan this properly", "spec-driven", "create requirements", "design document", "task breakdown", "before we start coding".
Persistent schema-driven running log with three-component architecture - quick-capture ideas, AI auto-detection, and backlog review librarian
Break down, design, and structure features into implementable tasks for Photo Map MVP. Use when planning new features, creating user stories, defining API endpoints, structuring implementation phases, organizing project tasks, or designing feature breakdowns.
Apply MAKER (Massively Decomposed Agentic Processes) to solve long sequential tasks using task decomposition, multi-agent voting, and error correction. Use when facing complex multi-step problems, sequential planning, constraint satisfaction, or tasks requiring many consecutive decisions.
Document and manage architectural decisions using ADRs. Supports Y-statement and traditional ADR formats. Use when creating, reviewing, or searching decision records.
Meta-skill orchestrating 7 atomic skills into unified workflows for intelligent development
Systematic approach for breaking down complex, high-level requests into atomic, executable steps to ensure precision and prevent overwhelm.
Review distributed systems patterns, concurrency, and resilience. Analyzes retry policies, idempotency, timeouts, circuit breakers, and race conditions. Use when reviewing async code, workers, queues, or distributed transactions.
Extract business rules (BR-*) from requirements - validation rules, business logic, error handling, and decision criteria. Use when disambiguating requirements to identify specific rules that can be autogenerated into validators and logic.
Design clean, maintainable APIs with good ergonomics. Use when asked to design or improve APIs.
Senior frontend architect + design-system quality bar (a11y, tokens, typography, Tailwind/shadcn or MUI)
Design systems, component libraries, responsive UI/UX, accessibility. Build premium interfaces that enterprise clients expect.
Guide for DDD strategic design - analyzing domains through structured questioning, conducting stakeholder interviews (PM/domain experts/users), and producing Bounded Context analysis, Context Maps, and Ubiquitous Language. Use when user needs help understanding domain boundaries, planning domain interviews, or structuring DDD strategic artifacts.
Opinionated UI constraints and patterns for building better interfaces. Focuses on accessibility, usability, and implementation best practices.
Provides expert database analysis, schema design review, and query optimization assessment. Use this skill when the user needs database architecture evaluation, query performance analysis, or data integrity review. Triggers include requests for database audit, schema review, query optimization, or when asked to evaluate database patterns. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.
