ck:cook

Orchestrates feature implementation workflows with subagents across phases and finalization steps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tonamson/please-done --skill ck-cook-tonamson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:cook
Source: https://github.com/tonamson/please-done/tree/main/ck/.opencode/skills/cook
Command: npx skills add https://github.com/tonamson/please-done --skill ck-cook-tonamson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates end-to-end feature development by orchestrating research, planning, implementation, testing, and finalization via a standardized workflow and subagents.

Core Features & Use Cases

  • End-to-end feature workflow orchestration with mode-based execution (interactive, auto, fast, parallel, no-test, code).
  • Delegates specialized tasks to subagents (researcher, planner, tester, code-reviewer, project-manager, docs-manager, git-manager) and enforces gates.
  • Plan synchronization, governance of reviews, and mandatory finalization steps to ensure consistency across plan and documentation.
  • Use Case: A team launches a new feature by defining tasks, assigning owners, executing in parallel when possible, and finalizing with reports and commits.

Quick Start

Invoke /ck:cook with a plan or task to start the smart feature implementation workflow.

Frequently Asked Questions about ck:cook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end feature implementation workflows for software teams?▼

You can automate feature implementation workflows by invoking the tool with a plan or task to start cross-phase orchestration. It handles research, planning, iterative development, testing, and finalization via subagent delegation and governance gates.

Can I execute feature development tasks in parallel during the implementation workflow?▼

Yes, parallel execution is supported as one of multiple execution modes alongside interactive, auto, fast, no-test, and code modes. The workflow delegates specialized tasks to subagents and enforces governance gates to synchronize plans across parallel tasks.

How does plan validation and synchronization work during feature development?▼

Plan validation occurs through governance gates enforced by delegated project-manager and code-reviewer subagents. Mandatory finalization steps synchronize plans, update documentation, and commit changes to ensure consistency across the entire feature implementation lifecycle.

Do I need to manually update documentation and commit changes after feature implementation?▼

No, manual updates are not needed because the workflow enforces mandatory finalization steps. It automatically delegates docs-manager and git-manager subagents to synchronize plans, update documentation, and commit changes at the end of the development lifecycle.

What specialized roles can be delegated when orchestrating smart feature workflows?▼

The workflow delegates specialized tasks to subagents including researcher, planner, tester, code-reviewer, project-manager, docs-manager, and git-manager. Each subagent enforces specific governance gates throughout the end-to-end feature implementation process.

When should I use the interactive execution mode for feature implementation?▼

Use interactive execution mode when you need step-by-step cross-phase orchestration with manual oversight. Alternatively, auto, fast, parallel, no-test, and code modes provide varying levels of automation for different feature implementation workflow requirements.