recipe-task
The recipe-task skill executes user-defined tasks by first consulting a rule-advisor agent to identify applicable rules and metacognitive patterns, then systematically works through the task using TaskCreate and TaskUpdate tools to manage execution steps. Use this skill when you need structured task execution that incorporates rule-based guidance, avoids known failure patterns, and maintains awareness of quality standards throughout implementation.
git clone --depth 1 https://github.com/shinpr/claude-code-workflows /tmp/recipe-task && cp -r /tmp/recipe-task/dev-workflows-fullstack/skills/recipe-task ~/.claude/skills/recipe-taskSKILL.md
# Task Execution with Metacognitive Analysis Task: $ARGUMENTS ## Mandatory Execution Process **Step 1: Rule Selection via rule-advisor (REQUIRED)** Invoke rule-advisor using Agent tool: - `subagent_type`: "dev-workflows-fullstack:rule-advisor" - `description`: "Rule selection" - `prompt`: "Task: $ARGUMENTS. Select appropriate rules and perform metacognitive analysis." **Step 2: Utilize rule-advisor Output** After receiving rule-advisor's JSON response, proceed with: 1. **Understand Task Essence** (from `taskAnalysis.essence`) - Focus on fundamental purpose, not surface-level work - Distinguish between "quick fix" vs "proper solution" 2. **Follow Selected Rules** (from `selectedRules`) - Review each selected rule section - Apply concrete procedures and guidelines 3. **Recognize Past Failures** (from `metaCognitiveGuidance.pastFailures`) - Apply countermeasures for known failure patterns - Use suggested alternative approaches 4. **Execute First Action** (from `metaCognitiveGuidance.firstStep`) - Start with recommended action - Use suggested tools first **Step 3: Create Task List with TaskCreate** Register work steps using TaskCreate. Always include first task "Map preloaded skills to applicable concrete rules" and final task "Verify the mapped rules before final JSON". Break down the task based on rule-advisor's guidance: - Reflect `taskAnalysis.essence` in task descriptions - Apply `metaCognitiveGuidance.firstStep` to first task - Restructure tasks considering `warningPatterns` - Set priorities based on dependency order and warningPatterns severity **Step 4: Execute Implementation** Proceed with task execution following: - Start with `metaCognitiveGuidance.firstStep` action from rule-advisor - Update task structure with TaskUpdate to reflect rule-advisor insights - Selected rules from rule-advisor - Task structure (managed via TaskCreate/TaskUpdate) - Quality standards defined in the selectedRules output from rule-advisor - Monitor warningPatterns flags throughout execution and adjust approach when triggered
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
Validates Design Doc compliance and implementation completeness from third-party perspective. Use PROACTIVELY after implementation completes or when "review/implementation check/compliance" is mentioned. Provides acceptance criteria validation and quality reports.
Validates consistency between PRD/Design Doc and code implementation. Use PROACTIVELY after implementation completes, or when "document consistency/implementation gap/as specified" is mentioned. Uses multi-source evidence matching to identify discrepancies.
Analyzes existing codebase objectively for facts about implementation, user behavior patterns, and technical architecture. Use when existing code needs to be understood without hypothesis bias. Invoked before Design Doc creation to produce focused guidance for technical designers.
Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.
Reviews document consistency and completeness, providing approval decisions. Use PROACTIVELY after PRD/UI Spec/Design Doc/work plan creation, or when "document review/approval/check" is mentioned. Detects contradictions and rule violations with improvement suggestions.
Verifies consistency between test skeleton comments and implementation code. Use PROACTIVELY after test implementation completes, or when "test review/skeleton verification" is mentioned. Returns quality reports with failing items and fix instructions.
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports only observations without proposing solutions.