daic-mode-guidance
Explain the DAIC (Discuss-Align-Implement-Check) workflow, help users understand current mode, what's allowed in each mode, and how to transition between modes - ANALYSIS-ONLY skill
Explain the DAIC (Discuss-Align-Implement-Check) workflow, help users understand current mode, what's allowed in each mode, and how to transition between modes - ANALYSIS-ONLY skill
Step-by-step guide for implementing new features in laneweaverTMS, orchestrating use of specialized skills and agents for database, backend, and frontend work.
This skill should be used when the user asks to "create user stories", "write user stories", "break down epic into stories", "define user stories", "what stories do I need", "apply INVEST criteria", "write acceptance criteria", "split a large story", "story is too big", "story splitting", or when decomposing epics into specific, valuable user stories.
Use this skill when discussing features, planning work, or when users describe what they want to build. Guides MVP thinking - focusing on "what's the minimum to make this work?" rather than comprehensive solutions. Triggers on phrases like "help me think through this feature", "what should we build first?", "how should we scope this?", or any feature planning discussion.
Map customer journeys to optimize touchpoints and experiences
Learn how to create effective project skills following opence conventions.
Reports implementation status of project components with evidence. Use when asked about what's done, in progress, or planned for a project.
Use when reviewing design documents, technical specifications, or architecture docs before implementation planning
Create feature implementation plans before development. Captures requirements, acceptance criteria, non-goals, risks, and implementation complexity in structured markdown. Use when starting a new feature to ensure scope clarity and implementation guidance.
Use this skill when discussing features, planning work, or when users describe what they want to build. Guides MVP thinking - focusing on "what's the minimum to make this work?" rather than comprehensive solutions. Triggers on phrases like "help me think through this feature", "what should we build first?", "how should we scope this?", or any feature planning discussion.
Ask clarifying questions to resolve underspecified requests before starting work.
Guidelines for transforming descriptive tasks into technical breakdowns with main tasks (product-focused, well-formatted JIRA tickets) and subtasks (implementation-focused, technical chunks). Scope: task generation, consolidation, FE/BE separation, point estimation (0.1-5 scale), acceptance criteria. Triggers: "task", "breakdown", "subtask", "main task", "ticket", "JIRA", "estimation", "point".
Refine ideas into detailed designs through Socratic dialogue. Use when: user has rough idea, needs to clarify requirements, explore approaches. Triggers: "brainstorm", "discuss idea", "I'm thinking about", "what if", "help me think through", "explore options", "/brainstorm".
Create comprehensive, multi-phase implementation plans for features. Detects technology stack, interviews user, researches current best practices, generates parallelizable phases with poker estimates, TDD-first acceptance criteria, quality gates (linters/formatters/typecheckers), and detailed code deltas. Use when starting significant features, epics, or complex tasks.
Create, deploy, and analyze Net Promoter Score surveys to measure customer loyalty
Use when creating new stories, writing requirements, or drafting feature specifications. Triggers on requests to create stories, write specs, or plan new features.
High-level Product Management analysis using first-principles. Jumps out of code implementation to analyze product functionality, design, and strategic structure.
This skill should be used when the user asks to "discover vision", "create a vision", "define product vision", "document vision", "what should my vision be", "help me with vision", "start requirements from scratch", "begin new product planning", "define product direction", "establish product vision", or when starting a new requirements project and needs to establish the foundational product vision before identifying epics or stories.
Track project milestones with progress monitoring, deadline management, and stakeholder communication
Skill for implementing features based on documentation, bridging technical specs (API, ERD, Stories) and code using a Test-Driven Approach.
This skill should be used when the user has a large, complex task requiring: (1) multi-file or multi-step implementation, (2) major refactoring or architecture changes, (3) new feature spanning multiple components. This skill should NOT be used for simple fixes, single-file edits, or quick questions. Activates strict verification with planning, success criteria, and evidence collection.
This skill should be used when the user asks to "prioritize requirements", "prioritize epics", "prioritize stories", "prioritize tasks", "prioritize backlog", "use MoSCoW", "apply MoSCoW priorities", "assign priorities", "set priority labels", "rank features", "what should I build first", "what's most important", "order by importance", "must have vs should have", or when they need to determine the priority order of epics, user stories, or tasks using the MoSCoW framework.
Facilitate productive team retrospectives with structured formats and actionable improvement outcomes