cs-feat-accept

Verifies feature implementations against design docs and produces acceptance reports.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/wildlily1021/XW_Software --skill cs-feat-accept-wildlily1021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-feat-accept
Source: https://github.com/wildlily1021/XW_Software/tree/main/.agents/skills/cs-feat-accept
Command: npx skills add https://github.com/wildlily1021/XW_Software --skill cs-feat-accept-wildlily1021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a feature is coded, teams often skip structured acceptance: implementations drift from the design, architecture docs go stale, requirement records fall out of sync, and roadmap status is never updated. This Skill closes the loop by enforcing a rigorous, checklist-driven acceptance workflow before merge. ## Core Features & Use Cases - Design Conformance Audit: Compares the actual code against the design document section by section (interface contracts, behaviors, mount points, terminology), fixing deviations in code rather than merely noting them. - Documentation Write-Back: Merges stable, system-visible changes into architecture docs, backfills or updates requirement records, and marks roadmap items as done in items.yaml with main-document synchronization. - Acceptance Report Generation: Produces a structured {slug}-acceptance.md report covering 9 mandatory sections, with resumable progress tracked via a checklist YAML file. - Use Case: A developer finishes implementing a serial-port data monitor feature and says "功能写完了验收一下". The Skill walks through interface verification, browser-based UI checks, mount-point grep audits, architecture merging, and roadmap updates, then delivers a complete acceptance report for final user review. ## Quick Start Tell the AI "这个功能写完了,帮我做验收并出验收报告" to start the full acceptance workflow against the existing design document.

Frequently Asked Questions about cs-feat-accept

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

FAQPage Schema
How do I verify a feature implementation matches its design document?▼

Run the acceptance workflow which compares code against the design doc section by section: interface contracts, behavior decisions, mount points, and terminology. Deviations are fixed in code or backfilled into the design doc rather than merely recorded as known issues.

What is a feature acceptance report and when should I create one?▼

An acceptance report is a structured 9-section document created after implementation is complete but before merge. It records interface verification, scenario testing results, architecture merging, and requirement or roadmap write-backs so future work can trace what was confirmed.

Does this acceptance workflow work with frontend UI changes?▼

Yes, frontend changes require mandatory browser-based visual verification in addition to type checking. Passing typecheck alone is explicitly called out as insufficient; each UI area must be confirmed in a real browser with evidence recorded.

What happens if the acceptance checklist has pending items?▼

If the implementation checklist contains pending steps, the workflow stops and returns to the implementation stage. Acceptance only proceeds when all implementation steps are done and all acceptance checks are in pending state ready for verification.

Can I resume an interrupted acceptance review?▼

Yes, the workflow supports breakpoint recovery. If a partially filled acceptance report exists, it resumes from the next unfinished section and skips checks already marked as passed, reporting where it is continuing from.