implement

Execute feature spec tasks sequentially with linting, testing, and verification.

Updated Aug 23, 2026

Search Tags:#testing #linting #task-management #specs #feature-implementation #living-documentation

Ready to run

npx skills add https://github.com/meganide/claude --skill implement-meganide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/meganide/claude/tree/main/skills/implement
Command: npx skills add https://github.com/meganide/claude --skill implement-meganide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage feature implementation by executing tasks from a feature spec one at a time, updating living documentation as work progresses.

Core Features & Use Cases

Task-driven execution: Work through tasks sequentially, updating task progress as you go.
Living documentation: Keeps specs/docs in sync with implementation.
Guided workflow: Provides structured task fields (title, context, files, success, steps) and a defined process for linting, testing, and verification.

Quick Start

To start implementing a feature, run the command for the interactive mode, review the first pending task, and proceed step by step.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I keep feature specs in sync while implementing tasks?▼

You keep feature specs in sync by executing tasks from a feature spec sequentially, updating living documentation as progress is tracked task by task throughout the software project.

What is the best way to track feature implementation progress task by task?▼

The best way to track feature implementation progress task by task is using structured task fields including title, context, files, success criteria, and steps, requiring explicit verification before marking any task complete.

How do I enforce linting and testing before marking a task complete?▼

Enforcing linting and testing before marking a task complete involves following a guided workflow that requires explicit verification of automated testing and linting success within the structured task steps.

What fields are required for task-driven feature implementation?▼

Required fields for task-driven feature implementation include title, context, files, success criteria, and steps, ensuring software projects with live specs maintain structured progress tracking.

Can I use living documentation for software projects with live specs?▼

Yes, you can use living documentation for software projects with live specs by executing tasks one at a time and updating the documentation as work progresses to keep it continuously synchronized.

When do I need explicit verification for task management in feature implementation?▼

You need explicit verification for task management in feature implementation whenever a task is completed, requiring linting, testing, and verification checks before the task is marked complete to maintain live specs.