Implementation Checklist Skill

Generate implementation checklists from feature specification documents.

2|1|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/1ambda/dataops-platform --skill implementation-checklist-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Implementation Checklist Skill
Source: https://github.com/1ambda/dataops-platform/tree/main/.copilot/skills/implementation-checklist
Command: npx skills add https://github.com/1ambda/dataops-platform --skill implementation-checklist-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the issue of incomplete feature implementation by automatically generating a checklist of required components (APIs, CLI commands, models, tests, etc.) based on a FEATURE document, ensuring all aspects of a feature are considered and implemented before declaring completion.

Core Features & Use Cases

  • Automated Checklist Generation: Parses FEATURE documents to identify API methods, CLI commands, data models, exceptions, and test requirements.
  • Verification Guidance: Provides grep commands and file checks to verify the existence and correctness of implemented components.
  • Progress Tracking: Supports phased checklists for planning, tracking, and final verification of feature implementation.
  • Use Case: Before a developer declares a new API endpoint complete, this Skill generates a checklist that includes not only the API method itself but also its corresponding CLI command, necessary model definitions, exception handling, and unit tests, ensuring a holistic implementation.

Quick Start

Use the implementation-checklist skill to generate a checklist for the 'FEATURE_USER_AUTH.md' document.

Frequently Asked Questions about Implementation Checklist Skill

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

FAQPage Schema
How do I generate an implementation checklist from a feature specification document?

To generate an implementation checklist, provide a feature specification document to the skill, which scans for API endpoints, CLI commands, data models, exceptions, and test cases to produce a comprehensive verification list. It ensures all defined components are implemented before completion.

What is the best way to verify feature implementation completeness before merging?

The best way to verify feature implementation completeness is using an automated checklist that provides grep commands and file checks to confirm the existence and correctness of API methods, models, exception handling, and unit tests defined in your specification.

How does automated checklist generation handle cross-component consistency in software engineering?

Automated checklist generation handles cross-component consistency by enforcing adherence to defined development standards, scanning the feature specification to map API endpoints to necessary CLI commands, data models, and corresponding test requirements for holistic implementation.

Can I use shell commands to verify the existence of API endpoints and data models?

Yes, you can use shell commands to verify the existence of API endpoints and data models. The skill provides specific grep commands and file checks to validate that all implemented components match the requirements parsed from the feature specification document.

Do I need a specific format for my feature specification document to generate a development checklist?

You need a feature specification document detailing required components like API methods, CLI commands, data models, exceptions, and test cases. The skill parses this document to automatically generate a phased checklist for planning, tracking, and final verification.