Automate end-to-end feature implementation through planning, coding, testing, and verification.
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-cook-edgehunt
Please help me install this Agent Skill. Skill: ck:cook Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/cook Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-cook-edgehunt
End-to-end feature implementation work is orchestrated: detecting intent, planning, coding, testing, and finalizing, to reduce manual coordination overhead.
Provide a natural-language feature request; the skill will detect intent, plan, implement, and verify.
High-intent search queries and answers about installing and using this skill.
The workflow detects intent from your natural-language feature request and routes it to an appropriate execution mode, such as interactive, auto, fast, parallel, or no-test. It then coordinates plan-driven execution by spawning subagents to handle research, UI work, testing, and code review.
Plan-driven execution generates or loads a structured plan and executes it in phases with mandatory review gates. This ensures complex software features are implemented systematically by coordinating multi-agent teams through each stage before finalizing and committing changes.
Yes, subagent orchestration works with code review and testing by spawning dedicated subagents via Task tools. These subagents collaborate to handle research, planning, UI work, testing, and finalization, ensuring all verification steps are covered before changes are committed.
Yes, you can use fast, parallel, auto, or no-test modes to implement features without manual coordination. The workflow detects your intent and automatically delegates tasks to subagents, reducing overhead by managing research, coding, and verification across multi-agent teams.
No-test mode skips the testing and verification phases of plan-based execution, meaning changes are implemented and finalized without automated test validation. You should avoid this mode for complex features requiring strict verification gates or when code review subagents need test results.
Yes, structured frontmatter metadata is required to run the ck:cook skill, along with references for rules and mandatory subagent delegation via Task tools. These elements coordinate the research, planning, UI work, testing, and finalization phases across multi-agent teams.
slamb2kConsolidate PocketSmith data into rule-driven financial workflows with YAML rules.
rocky2431Sync feature-status.json with task completion and test results.
morodomiOrchestrate cross-layer parallel TDD execution across Agent Teams.
dthuy62Turn a task or plan into a controlled software delivery workflow with planning, implementation, testing, review, and finalization.
