cs-feat-accept

Validate design-implementation alignment and generate an acceptance report.

1.1k|82|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-feat-accept
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-feat-accept
Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-feat-accept
Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-feat-accept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill closes the feature development lifecycle by validating that the implemented work aligns with the design, and by updating project governance documents (architecture, requirements, and roadmap) to reflect the completed work.

Core Features & Use Cases

  • Ensures implementational alignment with the design specifications and flags deviations for immediate correction.
  • Updates architecture-related references to consolidate the current state of the feature.
  • Generates an acceptance report that records decisions, validation steps, and status transitions for audit and handoff.

Quick Start

Call cs-feat-accept after the feature implementation is complete to generate the acceptance report and synchronize governance artifacts.

Frequently Asked Questions about cs-feat-accept

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

FAQPage Schema
How do I automate feature acceptance and update project governance documents?

Automate feature acceptance by validating implementation alignment with design specifications, then synchronizing architecture, requirements, and roadmap documents to reflect completed work.

What is included in an automated feature acceptance report?

An acceptance report records validation steps, design deviations, status transitions, and decisions for audit and handoff after feature implementation is complete.

How do I validate implementation alignment with design specifications before closing a feature?

Validate implementation alignment by comparing completed work against design specifications, automatically flagging any deviations for immediate correction before final approval.

When should I trigger the feature acceptance workflow in the development lifecycle?

Trigger feature acceptance after implementation is fully complete to validate alignment, generate acceptance reports, and backfill requirement and roadmap tracking artifacts.

Can I use this feature governance workflow without dependencies or external components?

Yes, the feature acceptance workflow operates independently without external dependencies or components, validating alignment and generating reports using existing artifacts.

What happens if the implementation deviates from the architecture roadmap during acceptance?

When implementation deviates from the design, the acceptance process flags the deviation for immediate correction and records the status transition in the generated report.