# Duc01226 Easyplatform Cook Auto Parallel > > **[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 ATTENTION ask user whether to skip. - Skill: `tomevault-io/duc01226-easyplatform-cook-auto-parallel` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/duc01226-easyplatform-cook-auto-parallel` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/duc01226-easyplatform-cook-auto-parallel/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/duc01226-easyplatform-cook-auto-parallel --- > **[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 ATTENTION ask user whether to skip. > **Understand Code First** — HARD-GATE: Do NOT write, plan, or fix until you READ existing code. > > 1. Search 3+ similar patterns (`grep`/`glob`) — cite `file:line` evidence > 2. Read existing files in target area — understand structure, base classes, conventions > 3. Run `python .claude/scripts/code_graph trace --direction both --json` when `.code-graph/graph.db` exists > 4. Map dependencies via `connections` or `callers_of` — know what depends on your target > 5. Write investigation to `.ai/workspace/analysis/` for non-trivial tasks (3+ files) > 6. Re-read analysis file before implementing — never work from memory alone > 7. NEVER invent new patterns when existing ones work — match exactly or document deviation > > **BLOCKED until:** `- [ ]` Read target files `- [ ]` Grep 3+ patterns `- [ ]` Graph trace (if graph.db exists) `- [ ]` Assumptions verified with evidence - `docs/project-reference/domain-entities-reference.md` — Domain entity catalog, relationships, cross-service sync (read when task involves business entities/models) (content auto-injected by hook — check for [Injected: ...] header before reading) - `docs/test-specs/` — Test specifications by module (read existing TCs; generate/update test specs via `/tdd-spec` after implementation) > **Plan Quality** — Every plan phase MUST ATTENTION include test specifications. > > 1. Add `## Test Specifications` section with TC-{FEAT}-{NNN} IDs to every phase file > 2. Map every functional requirement to ≥1 TC (or explicit `TBD` with rationale) > 3. TC IDs follow `TC-{FEATURE}-{NNN}` format — reference by ID, never embed full content > 4. Before any new workflow step: call `TaskList` and re-read the phase file > 5. On context compaction: call `TaskList` FIRST — never create duplicate tasks > 6. Verify TC satisfaction per phase before marking complete (evidence must be `file:line`, not TBD) > > **Mode:** TDD-first → reference existing TCs with `Evidence: TBD`. Implement-first → use TBD → `/tdd-spec` fills after. > **Rationalization Prevention** — AI skips steps via these evasions. Recognize and reject: > > | Evasion | Rebuttal | > | ---------------------------- | ------------------------------------------------------------- | > | "Too simple for a plan" | Simple + wrong assumptions = wasted time. Plan anyway. | > | "I'll test after" | RED before GREEN. Write/verify test first. | > | "Already searched" | Show grep evidence with `file:line`. No proof = no search. | > | "Just do it" | Still need TaskCreate. Skip depth, never skip tracking. | > | "Just a small fix" | Small fix in wrong location cascades. Verify file:line first. | > | "Code is self-explanatory" | Future readers need evidence trail. Document anyway. | > | "Combine steps to save time" | Combined steps dilute focus. Each step has distinct purpose. | > **Red Flag Stop Conditions** — STOP and escalate to user via AskUserQuestion when: > > 1. Confidence drops below 60% on any critical decision > 2. Changes would affect >20 files (blast radius too large) > 3. Cross-service boundary is being crossed > 4. Security-sensitive code (auth, crypto, PII handling) > 5. Breaking change detected (interface, API contract, DB schema) > 6. Test coverage would decrease after changes > 7. Approach requires technology/pattern not in the project > > **NEVER proceed past a red flag without explicit user approval.** > **Skill Variant:** Variant of `/cook` — autonomous parallel execution with fullstack-developer subagents. ## Quick Summary **Goal:** Plan parallel-executable phases and dispatch to fullstack-developer subagents for concurrent implementation. **Workflow:** 1. **Plan** — Create plan with parallel-executable phases (strict file ownership) 2. **Dispatch** — Launch fullstack-developer subagents per phase 3. **Merge** — Integrate results and verify **Key Rules:** - Each subagent owns specific files; no cross-boundary edits - Autonomous mode: no user confirmation between phases - Break work into todo tasks; add final self-review task **Ultrathink parallel** to implement: $ARGUMENTS **IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision. **Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).** ## Workflow ### 1. Research (Optional) - Use max 2 `researcher` agents in parallel if tasks complex - Use `/scout-ext` to search codebase - Keep reports ≤150 lines - **External Memory**: Write research to `.ai/workspace/analysis/{task-name}.analysis.md`. Re-read before parallel execution. ### 2. Parallel Planning - Trigger `/plan-parallel ` - Wait for plan with dependency graph, execution strategy, file ownership matrix ### 3. Parallel Implementation - Read `plan.md` for dependency graph - Launch multiple `fullstack-developer` agents in PARALLEL for concurrent phases - Example: "Phases 1-3 parallel" → launch 3 agents simultaneously - Pass phase file path: `{plan-dir}/phase-XX-*.md` - Include environment info - Wait for all parallel phases complete before dependent phases - Sequential phases: launch one agent at a time ### 4. Testing - Use `tester` subagent for full test suite - NO fake data/mocks/cheats - If fail: use `debugger`, fix, repeat ### 5. Code Review - Use `code-reviewer` for all changes - If critical issues: fix, retest ### 6. Project Management & Docs - If approved: use `project-manager` + `docs-manager` in parallel - Update plan files, docs, roadmap - If rejected: fix and repeat ### 7. Final Report - Summary of all parallel phases - Guide to get started - Ask to commit (use `git-manager` if yes) **Example:** Phases 1-3 parallel → Launch 3 fullstack-developer agents → Wait → Phase 4 sequential --- ## Next Steps (Standalone: MUST ATTENTION ask user via `AskUserQuestion`. Skip if inside workflow.) > **MANDATORY IMPORTANT MUST ATTENTION — NO EXCEPTIONS:** If this skill was called **outside a workflow**, you MUST ATTENTION use `AskUserQuestion` to present these options. Do NOT skip because the task seems "simple" or "obvious" — the user decides: - **"Proceed with full workflow (Recommended)"** — I'll detect the best workflow to continue from here (feature implemented). This ensures review, testing, and docs steps aren't skipped. - **"/code-simplifier"** — Simplify and clean up implementation - **"/workflow-review-changes"** — Review changes before commit - **"Skip, continue manually"** — user decides > If already inside a workflow, skip — the workflow handles sequencing. ## Closing Reminders - **MANDATORY IMPORTANT MUST ATTENTION** break work into small todo tasks using `TaskCreate` BEFORE starting - **MANDATORY IMPORTANT MUST ATTENTION** search codebase for 3+ similar patterns before creating new code - **MANDATORY IMPORTANT MUST ATTENTION** cite `file:line` evidence for every claim (confidence >80% to act) - **MANDATORY IMPORTANT MUST ATTENTION** add a final review todo task to verify work quality - **MANDATORY IMPORTANT MUST ATTENTION** validate decisions with user via `AskUserQuestion` — never auto-decide - **MANDATORY IMPORTANT MUST ATTENTION** search 3+ existing patterns and read code BEFORE any modification. Run graph trace when graph.db exists. - **MANDATORY IMPORTANT MUST ATTENTION** include `## Test Specifications` with TC IDs per phase. Call `TaskList` before creating new tasks. - **MANDATORY IMPORTANT MUST ATTENTION** follow ALL steps regardless of perceived simplicity. "Too simple to plan" is an evasion, not a reason. - **MANDATORY IMPORTANT MUST ATTENTION** STOP after 3 failed fix attempts. Report all attempts, ask user before continuing. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/duc01226) — claim your Tome and manage your conversions.