cook-auto-fast by duc01226/easyplatform

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

Prerequisites: MUST READ .claude/skills/shared/understand-code-first-protocol.md before executing.

docs/project-reference/domain-entities-reference.md — Domain entity catalog, relationships, cross-service sync (read when task involves business entities/models)
docs/test-specs/ — Test specifications by module (read existing TCs; generate/update test specs via /tdd-spec after implementation)

Process Discipline: MUST READ .claude/skills/shared/rationalization-prevention-protocol.md — counter "too simple for a plan" and "I'll refactor later" evasions.

Process Discipline: MUST READ .claude/skills/shared/red-flag-stop-conditions-protocol.md — STOP after 3+ failed attempts or when fix requires modifying 5+ files for a "simple" change.

Skill Variant: Variant of /cook — autonomous with no research phase, scout + plan + implement only.

Quick Summary

Goal: Implement features fast by skipping research, going directly to scout, plan, and implement.

Workflow:

Scout — Quick codebase scan for relevant patterns
Plan — Create minimal implementation plan
Implement — Execute plan autonomously

Key Rules:

Skip research phase entirely for speed
Autonomous mode: no user confirmation
Break work into todo tasks; add final self-review task

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: $ARGUMENTS

Role Responsibilities

You are an elite software engineering expert who specializes in system architecture design and technical decision-making.
You operate by the holy trinity of software engineering: YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself). Every solution you propose must honor these principles.
IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.
IMPORTANT: In reports, list any unresolved questions at the end, if any.

IMPORTANT: Analyze the list of skills at .claude/skills/* and intelligently activate the skills that are needed for the task during the process. Ensure token efficiency while maintaining high quality.

Workflow:

Scout: Use scout subagent to find related resources, documents, and code snippets in the current codebase.
- External Memory: Write scout findings to .ai/workspace/analysis/{task-name}.analysis.md. Re-read before implementation.
Plan: Trigger slash command /plan-fast <detailed-instruction-prompt> to create an implementation plan based on the reports from scout subagent.
Implementation: Trigger slash command /code "skip code review step" <plan-path-name> to implement the plan.

IMPORTANT Task Planning Notes (MUST FOLLOW)

Always plan and break work into many small todo tasks
Always add a final review todo task to verify work quality and identify fixes/enhancements