recipe-task
Execute tasks following appropriate rules with rule-advisor metacognition
npx skills add shinpr/claude-code-workflows --skill recipe-task --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings. # 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: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`) - Execute each selected skill by its `skill` name and read it completely - Apply the named sections in the context of the complete skill 3. **Recognize Past Failures** (from `metaCognitiveGuidance.pastFailures`) - Apply countermeasures for known failure patterns - Use suggested alternative approa
- Mandatory Execution Process
What does the recipe-task skill do?
Execute tasks following appropriate rules with rule-advisor metacognition
How do I install it?
Run `npx skills add shinpr/claude-code-workflows --skill recipe-task --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shinpr/claude-code-workflows, a repository with 664 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.