cs-feat-impl

Implements approved feature designs step-by-step following a checklist with structured completion reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When turning an approved design document into code, AI agents tend to over-engineer, silently refactor unrelated code, or push through situations the design never covered. This Skill enforces a disciplined implementation workflow that keeps code changes aligned with the approved plan and makes "stop and ask" the default behavior. ## Core Features & Use Cases - Checklist-Driven Execution: Executes steps from a {slug}-checklist.yaml in strict order, marking each step done only after its exit signal is verified. - Scope Guardrails: Blocks out-of-plan changes, patch-branch hacks, and unauthorized new terminology, routing discoveries into follow-up issues instead. - Standardized Completion Report: Produces a fixed-format report listing changed files, functions, plan deviations, and acceptance-scenario evidence for user review. - Use Case: After a feature design doc is approved, tell the agent to start implementation; it validates the design and checklist, executes each step, and reports back for review before acceptance. ## Quick Start Tell the agent "方案确认了,开始实现" to have it validate the approved design and checklist, then implement the feature step by step with a final structured report.

Frequently Asked Questions about cs-feat-impl

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

FAQPage Schema
How do I implement a feature from an approved design document?▼

Confirm the design doc has status approved and a valid checklist YAML, then start from step one. Each step is executed in order, marked done after its exit signal passes, and a structured completion report is produced for user review.

What is a feature implementation checklist workflow?▼

It is a step-driven process where a YAML checklist slices the design into 4-8 paradigm-dimension steps. The implementer decides which files to change per step, never merges or skips steps, and verifies each exit signal before proceeding.

What happens when the design does not cover a case found during coding?▼

The default action is to stop and return to the design discussion rather than add a patch branch. The gap is either added to the design, removed from scope, or recorded as a known legacy issue before coding continues.

Can I refactor unrelated code while implementing a feature?▼

No. Out-of-scope refactoring is recorded as a follow-up issue instead of being changed. Only dead code directly caused by the current change may be removed, keeping the feature PR focused and reviewable.

When should implementation be rejected and sent back to design?▼

Implementation is blocked when the design frontmatter is incomplete, required sections are missing, or the checklist file is absent or empty. These gaps must be fixed in the design phase first to avoid bypassing review checkpoints.