implement

Coordinate complex feature development through a phased plan-then-implement workflow.

36|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/ymahlau/bonni --skill implement-ymahlau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/ymahlau/bonni/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/ymahlau/bonni --skill implement-ymahlau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans and coordinates complex feature work by first sketching hypotheses, then validating, planning, and obtaining user alignment before parallel implementation by subagents.

Core Features & Use Cases

  • Structured five-phase workflow (Sketch, Explore, Plan, Implement, Verify) to manage complex changes.
  • Parallel execution with subagents to accelerate delivery while preserving guardrails and approvals.
  • Suitable for non-trivial features or changes requiring cross-team coordination and risk mitigation.

Quick Start

Provide a complete, plan-first implementation for a complex feature by initiating Phase 1 sketch, moving through exploration and planning, pausing for user approval, then executing in parallel subagents.

Frequently Asked Questions about implement

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

FAQPage Schema
What is a plan-then-implement workflow for complex feature development?

A plan-then-implement workflow structures complex feature development into phases: Sketch, Explore, Plan, Implement, and Verify. It validates hypotheses and secures user alignment before executing parallel subagents to deliver changes safely.

How do I coordinate parallel execution of subagents for software engineering tasks?

You coordinate parallel execution of subagents by isolating implementation tasks after a structured planning phase. This approach accelerates delivery of non-trivial features while preserving guardrails and requiring user approval before execution begins.

When do I need a structured phased workflow for software feature implementation?

You need a structured phased workflow for software feature implementation when managing non-trivial changes that require cross-team coordination, risk mitigation, and structured exploration. It ensures safe, auditable changes through user validation and parallelized implementation.

Can I use parallel subagents for cross-team feature planning and implementation?

Yes, you can use parallel subagents for cross-team feature implementation. The workflow mandates a planning phase to secure user approval, then dispatches isolated subagents for parallel execution to accelerate delivery while maintaining guardrails.

What is the best way to manage risk when implementing non-trivial software features?

The best way to manage risk when implementing non-trivial software features is applying a Sketch, Explore, Plan, Implement, and Verify workflow. It enforces user validation and isolates parallel subagent execution to ensure auditable changes.

Does the implementation workflow require user approval before executing changes?

Yes, the implementation workflow requires user approval before executing changes. After the Sketch, Explore, and Plan phases conclude, the process pauses for user validation before initiating parallel subagent implementation to ensure safe outcomes.