engineer

Implement the smallest viable change within approved scope from plan.md and RFCs.

13|1|Updated Feb 7, 2026

Search Tags:#implementation #verification #plan.md #contract #audit-trail #bounded-work #design-gate

Ready to run

npx skills add https://github.com/Thrimbda/legion-mind --skill engineer-thrimbda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: engineer
Source: https://github.com/Thrimbda/legion-mind/tree/main/skills/engineer
Command: npx skills add https://github.com/Thrimbda/legion-mind --skill engineer-thrimbda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce bounded implementation only after an approved contract and design gate exist, preventing scope creep and ensuring work aligns with verification and review processes.

Core Features & Use Cases

Read plan.md and any RFC/design sources to verify the scope before coding.
Implement the smallest viable change within the defined scope.
If the plan or design gate is not satisfied, escalate to brainstorm or spec-rfc instead of coding.
Handoff results to verify-change for validation and auditable traceability.

Quick Start

Review the plan.md and any RFCs, then implement the smallest viable change within the approved scope.

Frequently Asked Questions about engineer

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

FAQPage Schema

How do I prevent scope creep during software implementation after a design is approved?▼

Bounded implementation prevents scope creep by enforcing the approved design gate and contract before coding. It reads plan.md and RFC design sources to ensure changes stay strictly within the defined boundaries, returning the smallest viable change for validation.

What is a design gate in software engineering and when do I need it?▼

A design gate is an approved checkpoint, often involving an RFC or contract, required before implementation begins. You need it when plan.md is present to ensure coding work aligns with verification and review processes, preventing unbounded modifications.

How to implement the smallest viable change within an approved contract scope?▼

Review plan.md and any available RFC design sources to verify the approved scope, then implement only the smallest viable change that satisfies the contract. This ensures your work remains bounded and can be cleanly handed off to verification.

Do I need an approved RFC or plan.md before starting bounded implementation?▼

Yes, you need an approved contract and design gate, typically reflected in plan.md and an RFC, before starting. If these are not satisfied, you must escalate to brainstorming or spec-rfc phases rather than proceeding with coding.

What happens if the plan or design gate is not satisfied before implementation?▼

If the plan or design gate is not satisfied, bounded implementation escalates the work to brainstorm or spec-rfc stages instead of coding. This ensures proper scope definition and an approved contract exist before any implementation changes are made.

How do I hand off implementation results for verification and audit trail?▼

After implementing the smallest viable change within the defined scope, hand off the results to verify-change for validation. This ensures your implementation passes review processes and maintains auditable traceability throughout the workflow.