implement-spec

Select a spec file from .agents/plans/ and implement it with tests, typecheck, and lint.

1.8k|62|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/LibPDF-js/core --skill implement-spec-libpdf-js
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/LibPDF-js/core/tree/main/.opencode/skills/implement-spec
Command: npx skills add https://github.com/LibPDF-js/core --skill implement-spec-libpdf-js

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables autonomous implementation of project specifications by selecting the correct spec file from the plans directory, interpreting workflow requirements, and producing concrete code and tests.

Core Features & Use Cases

  • Spec selection automation: Identify the intended spec file when multiple specs exist, or request clarification.
  • End-to-end implementation: Read ARCHITECTURE.md and CODE_STYLE.md, plan tasks, implement features, and write tests.
  • Quality gates: Run tests, typecheck, and lint to ensure compliance with project standards.

Quick Start

Run the implement-spec process to automatically identify and implement the required spec from the .agents/plans/ directory for the active project.

Frequently Asked Questions about implement-spec

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

FAQPage Schema
How do I autonomously implement project specs from plans?

To autonomously implement project specs, this Skill identifies the correct spec file in .agents/plans/, loads ARCHITECTURE.md for context, and plans feature implementation using TodoWrite. It then writes code, generates tests, and runs typecheck and lint until all requirements pass.

What is the process for selecting the correct specification file when multiple specs exist?

Spec selection automation works by analyzing the current project context to identify the intended specification file within the .agents/plans/ directory. If the target spec remains ambiguous, the process pauses to request clarification before proceeding with implementation.

How to write tests and run typecheck after implementing a feature plan?

After implementing a feature plan, the process automatically writes corresponding tests and executes quality gates by running typecheck and lint. It iterates through this cycle until the code complies with all project standards and test requirements pass.

Does autonomous spec implementation require CODE_STYLE.md and ARCHITECTURE.md files?

Autonomous spec implementation relies on ARCHITECTURE.md to understand project structure and CODE_STYLE.md to ensure compliance. These files provide the necessary context for planning tasks and generating code that meets existing project standards.

What's the best way to automate software engineering tasks from specification documents?

Automating software engineering tasks from specification documents is best handled by a process that reads architectural guidelines, plans tasks via TodoWrite, implements features, and enforces quality gates through tests, typecheck, and lint iteration.

Why does autonomous spec implementation fail when architecture context is missing?

Autonomous spec implementation fails without architecture context because it depends on ARCHITECTURE.md to understand structure and CODE_STYLE.md for standards. Missing these files prevents accurate task planning, code generation, and compliance validation.