skills.rest
lucas-barake
lucas-barakeCOMMUNITY
Explore all skills by this author →
GitHub

implementer

Execute pre-investigated plans step-by-step with context validation and traceable logging.

Updated Aug 27, 2026
Search Tags:#automation#workflow#planning#ai#plans#implement#execute
One-click install
npx skills add https://github.com/lucas-barake/dotai --skill implementer-lucas-barake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementer
Source: https://github.com/lucas-barake/dotai/tree/main/canonical/skills/implementer
Command: npx skills add https://github.com/lucas-barake/dotai --skill implementer-lucas-barake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementer mode reduces the cognitive overhead and risk when executing pre-investigated plans by providing a guided, repeatable workflow that ensures plans are followed accurately and efficiently.

Core Features & Use Cases

  • Plan loading and context capture: Reads and analyzes the chosen plan from {{plans_dir}} before acting.
  • Context validation: Verifies all referenced files, tests, and dependencies to avoid surprises during execution.
  • Execution harness: Applies the plan step-by-step, updating state and logging progress for traceability.
  • Use Case: When a pre-approved plan exists for a code change, use this skill to implement it, validate results, and report outcomes.

Quick Start

Enter a plan path under {{plans_dir}} to initiate implementer mode and begin executing the plan immediately.

Frequently Asked Questions about implementer

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

FAQPage Schema
How do I execute pre-investigated plans for software engineering tasks accurately?▼

To execute pre-investigated plans accurately, you need a guided workflow that reads plan references, validates dependencies, and applies steps systematically to ensure reliable outcomes and traceable execution.

How do I validate context and dependencies before automating a code change workflow?▼

Validating context before automating a code change workflow involves verifying all referenced files, tests, and dependencies to avoid surprises during execution and ensure strict adherence to the plan.

What is the best way to ensure strict adherence to pre-approved plans during implementation?▼

The best way to ensure strict adherence to pre-approved plans is using an execution harness that applies the plan step-by-step, updating state and logging progress for complete traceability.

Can I reduce execution risk for complex software engineering plans?▼

You can reduce execution risk for complex software engineering plans by using a repeatable execution workflow that loads necessary context and validates all references before acting.

Does this workflow require a pre-approved plan before implementation begins?▼

Yes, this workflow requires a pre-approved plan path to initiate implementer mode, which then reads, validates, and applies the plan step-by-step to achieve reliable outcomes.

When do I need a repeatable execution workflow for code changes?▼

You need a repeatable execution workflow for code changes when you have pre-defined plans requiring strict adherence, cognitive overhead reduction, and traceable execution logging.

Related Skills

Explore More Software Engineering Skills→
omarluqomarluq
1

plan-review

Audit implementation plans for citations, completeness, and actionability.

Community
Advanced
beyondwenbeyondwen

receiving-code-review

Validate code-review feedback with clarifying questions and verification plans.

Community
Intermediate
tianzecntianzecn
2

dependency-check

Verify Chrome DevTools MCP and OpenRouter API key before frontend commands.

Community
Intermediate
afel6afel6

plan

Generate timestamped Markdown implementation plans without modifying repository files.

Community
Intermediate