implement

Apply scoped code changes with pre- and post-checks in a task directory.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/TbK0ng/mytrellis --skill implement-tbk0ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/TbK0ng/mytrellis/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/TbK0ng/mytrellis --skill implement-tbk0ng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to execute the implementation phase for a scoped task, ensuring changes are minimal, deterministic, and auditable.

Core Features & Use Cases

  • Deterministic implementation: apply only what the task requires, with explicit pre/post-checks.
  • Quality-first: run lint and typecheck, execute targeted tests, and append progress notes to the task directory.
  • Use Case: during a Codex pipeline task, implement the required feature with traceable commits and a concise implementation report.

Quick Start

Initiate the implementation phase by reviewing the injected context and applying minimal, verifiable code changes.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I execute deterministic code changes during a software implementation phase?

To execute deterministic code changes, apply scoped, minimal edits based on injected context and task artifacts within a dedicated task directory. This enforces pre_checks and post_checks to ensure auditable, verifiable modifications.

How do I run lint and typecheck checks for scoped software development tasks?

Run lint and typecheck checks by enforcing phase-specific post_checks after applying code changes. The workflow executes targeted tests and guides linting to maintain quality-first standards within the implementation phase.

What is the best way to ensure minimal and auditable edits in a Codex pipeline?

The best way to ensure auditable edits in a Codex pipeline is to apply only what the task requires. This involves using pre_checks, post_checks, and writing artifacts to append progress notes to the task directory.

Can I use phase-specific requirements to enforce pre and post checks during implementation?

Yes, you can enforce phase-specific requirements such as pre_checks, post_checks, writes_artifacts, and required_phase. These constraints guide linting, typecheck, and tests for precise code modifications.

Why does my implementation workflow require a dedicated task directory?

An implementation workflow requires a dedicated task directory to ensure changes are scoped, deterministic, and auditable. It isolates task artifacts and progress notes, maintaining strict boundaries for verifiable code edits.

Do I need injected context to apply verifiable code changes in a software pipeline?

Yes, injected context is required to apply minimal, verifiable code changes. It provides the necessary task artifacts and scope constraints that drive deterministic edits and pass the enforced post_checks.