implement-direct

Implement approved specs directly without test-driven development.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/opsMachine/OM-Agency --skill implement-direct
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-direct
Source: https://github.com/opsMachine/OM-Agency/tree/main/skills/implement-direct
Command: npx skills add https://github.com/opsMachine/OM-Agency --skill implement-direct

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements a feature from an approved spec using judgment, without writing tests first, to save time and avoid unnecessary overhead.

Core Features & Use Cases

  • Extracts the problem from the spec and identifies acceptance criteria, non-goals, and security considerations.
  • Plans the implementation with reference to existing conventions, then executes with judgment and manual verification.
  • Ideal for UI tweaks, simple CRUD, or features that require visual verification rather than automated testing.

Quick Start

Invoke the command /implement-direct path/to/spec.md to begin implementing from the approved spec.

Frequently Asked Questions about implement-direct

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

FAQPage Schema
How do I implement features from a spec without test-driven development?

You can implement features directly from an approved spec without TDD by extracting acceptance criteria and planning execution with manual verification, skipping automated tests to save time. This approach enables faster delivery for rapid prototyping and iterative changes.

When should I skip tests and implement features directly from a spec?

Skipping tests is ideal for UI tweaks, simple CRUD operations, or features verified visually rather than through automated testing. It suits rapid prototyping or iterative changes where manual verification is acceptable and faster delivery is required.

What is the process for direct feature implementation from an approved spec?

Direct feature implementation involves extracting the problem from an approved spec, identifying non-goals and security considerations, planning with existing conventions, executing with judgment, and performing manual verification. This process enforces spec requirements while avoiding test overhead.

Can I use direct implementation for complex features with security considerations?

Yes, direct implementation extracts and enforces security considerations from the approved spec. However, it applies judgment and manual verification instead of automated tests, making it best suited for simple CRUD, UI tweaks, and visually verifiable iterative changes.

What is the best way to speed up delivery for UI tweaks and simple CRUD features?

The best way to speed up delivery for UI tweaks and simple CRUD is implementing directly from an approved spec without writing tests first. By relying on manual visual verification and judgment, you avoid unnecessary test overhead while still enforcing spec requirements.