engineering-approach

Enforce design-before-code and verification-before-completion discipline in OpenCode tasks.

Updated Apr 24, 2026

Search Tags:#verification #orchestration #engineering #spec #sub-agent #design-before-code #scope-control

Ready to run

npx skills add https://github.com/michael-conrad/.opencode --skill engineering-approach-michael-conrad

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: engineering-approach
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/engineering-approach
Command: npx skills add https://github.com/michael-conrad/.opencode --skill engineering-approach-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering discipline checklist enforcing: understand before solving, design before implementing, verify before declaring complete, no scope creep.

Core Features & Use Cases

Enforces design-before-code discipline with explicit approvals
Orchestrates sub-agents and inline constraint checks
Facilitates rigorous verification and scope-management across large specs

Quick Start

Invoke the engineering-approach skill to verify problem understanding and document a design before coding.

Frequently Asked Questions about engineering-approach

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

FAQPage Schema

How do I enforce design before coding in spec-driven development?▼

Enforcing design before coding requires explicit approvals and constraint checks to verify problem understanding before any implementation begins. This approach ensures you document a design and validate the scope before writing code.

What is the best way to prevent scope creep during complex engineering changes?▼

Preventing scope creep during complex changes requires rigorous scope-management facilitated by sub-agent orchestration and inline constraint checks. This ensures all modifications stay strictly within the documented spec boundaries.

How does sub-agent routing work for complex spec verification?▼

Sub-agent routing for spec verification works by orchestrating specialized sub-agents and applying inline constraint checks across large specs. This validates that implementations meet design requirements before any task is declared complete.

Can I use an engineering discipline checklist to verify task completion?▼

Yes, an engineering discipline checklist verifies task completion by enforcing mandatory verification steps before declaring work done. It validates that you understood the problem, documented the design, and controlled the scope.

Does design review discipline work well for large software engineering specs?▼

Design review discipline works effectively for large software engineering specs by applying mandatory task discipline and rigorous verification. It orchestrates sub-agents to manage complexity and ensure thorough scope control across changes.