skills.rest
daudaudinang
daudaudinangCOMMUNITY
Explore all skills by this author →
GitHub

implement-plan

Implement a canonical LP plan within an ownership boundary and generate an execution contract.

Updated Apr 14, 2026
Search Tags:#automation#workflow#verification#ownership#plan#implement
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill implement-plan-daudaudinang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/implement-plan
Command: npx skills add https://github.com/daudaudinang/vibecode --skill implement-plan-daudaudinang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Worker-only skill to implement one canonical LP plan or phase within boundary and ownership, returning verifiable execution results.

Core Features & Use Cases

  • Boundary-respecting implementation: edits only owned files within the current plan scope.
  • Verification-driven output: produces explicit evidence and contract data to hand off to orchestrator.
  • Phase/plan scope support: handles plan or phase with dependency awareness and non-blocking behavior.

Quick Start

Provide the owned plan package and manifests to start implementing the plan within its boundaries.

Frequently Asked Questions about implement-plan

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

FAQPage Schema
How do I automate plan implementation within strict file ownership boundaries?▼

Automating plan implementation within boundaries requires providing a plan package with manifests, which the worker-only context executes by editing owned files and generating a formal execution contract.

What manifests do I need to provide to start implementing a plan phase?▼

To start implementing a plan phase, you need to provide plan.md, spec.md, ownership.json, and dependency-graph.json to satisfy the input requirements and define the execution scope.

How does dependency handling work when implementing a canonical plan?▼

Dependency handling during plan implementation processes the dependency-graph.json input to maintain phase scope awareness and execute with non-blocking behavior across defined ownership boundaries.

Can I use this worker-only execution context for plans outside my ownership boundary?▼

No, this worker-only execution context applies boundary-respecting implementation that edits only owned files within the current plan scope, preventing modifications outside your defined ownership boundary.

What verification output is generated after implementing a plan phase?▼

After implementing a plan phase, the process produces verification-driven output including explicit evidence and a formal 03-implement-plan execution contract to hand off to the orchestrator.

Related Skills

Explore More Software Engineering Skills→
daudaudinangdaudaudinang

review-plan

Review LP plan packages for gaps, ambiguities, and risks.

Community
Advanced
intent-integrity-chainintent-integrity-chain
47

iikit-03-plan

Translate a feature specification into a formal implementation plan with artifacts.

Official
Advanced
devs6186devs6186

do

Coordinate subagents across multi-phase plans with verification gates.

Community
Advanced
gihwan-devgihwan-dev

implement-task

Execute approved task slices from task.yaml bundles or PLAN.md files.

Community
Advanced