feature-implementing

Execute feature plans into validated code with task checklists and handoff summaries.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/WASD6570/crypto-monitor --skill feature-implementing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implementing
Source: https://github.com/WASD6570/crypto-monitor/tree/main/.agents/skills/feature-implementing
Command: npx skills add https://github.com/WASD6570/crypto-monitor --skill feature-implementing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns written feature plans into small, validated code changes and clear handoffs so implementation stalls are minimized and progress is reproducible.

Core Features & Use Cases

  • Enforces strict, step-by-step execution of feature plans stored under plans/{feature_name}/ to ensure safe, reviewable edits.
  • Maintains a built-in task checklist per step with Outcome, Files, Command, and Accepts to drive implementation and validation.
  • Provides end-of-step hygiene and handoff summaries that list completed work, next tasks, blockers, and validation artifacts for seamless team handoffs.
  • Use case: implement a multi-file React + Go feature by following 00-overview.md, creating granular tasks for the current step, running stack-appropriate validation, and logging the handoff when pausing.

Quick Start

Locate the active plan in plans/{feature_name}/, read 00-overview.md, create the task checklist for the first step, implement the next unchecked task, run the step's validation command, and record the handoff summary.

Frequently Asked Questions about feature-implementing

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

FAQPage Schema
How do I execute feature plans into validated code in a monorepo?

To execute feature plans into validated code, apply stepwise execution to plans stored in plans/{feature_name}/ by generating a task checklist for each step, implementing edits, running localized validation commands, and recording persistent handoff summaries.

How does stepwise execution with task checklists work for multi-language features?

Stepwise execution works by enforcing strict step ordering for multi-language features, requiring each task checklist to define Outcome, Files, Command, and Accepts criteria before advancing to the next step.

What is the best way to manage handoff state when pausing multi-file feature implementation?

The best way to manage handoff state when pausing multi-file feature implementation is to generate end-of-step handoff summaries that list completed work, next tasks, blockers, and validation artifacts for seamless team transitions.

Can I use localized validation commands for different stacks within a single feature plan?

Yes, you can use localized validation commands for different stacks within a single feature plan. The stepwise execution process supports running stack-appropriate validation commands tailored to each specific technology in the monorepo.

Do I need a specific folder structure for feature implementation task checklists?

Yes, you need a specific folder structure where feature plans reside in plans/{feature_name}/ and include an 00-overview.md file to initiate the stepwise task checklist generation and execution workflow.