impl

Original：🇨🇳 Chinese

Translated

Proceed with implementation based on the TODO list in Spec.md. Execute review→check→commit after each task is completed.

1installs

Sourcemyuon/ccskills

Added on2026-02-09

NPX Install

npx skill4agent add myuon/ccskills impl

SKILL.md Content (Chinese)

View Translation Comparison →

Implementation Workflow

A skill that proceeds with implementation in order based on the TODO list created in

/spec

.

Prerequisites

Spec.md has been created via
```
/spec
```
Tasks have been registered in TodoWrite

Step 0: Initial Setup (First-time only)

Before starting implementation, confirm the review and check methods using AskUserQuestion.

Question 1: Review Method

header: "Review"
question: "How will code reviews be conducted?"
options:
  - label: "Self-review (Default)"
    description: "Check from the perspectives of DRY, complexity, specification compliance, and security"
  - label: "/review スキルを使用"
    description: "Invoke the project's review skill"
  - label: "Skip"
    description: "Proceed without review"

Question 2: Check Method

header: "Check"
question: "Please provide the pre-commit check command"
options:
  - label: "Auto-detection"
    description: "Detect from package.json, Makefile, etc."
  - label: "npm run lint && npm run test"
    description: "Standard npm scripts"
  - label: "make check"
    description: "check target in Makefile"

If the user selects "Other", ask them to enter the specific command.

Workflow

Execute the following cycle for each TODO:

implement → review → check → commit → next

1. Implement

Change the next pending task in TodoWrite to in_progress
Refer to the corresponding Acceptance Criteria in Spec.md
Implement the required code

2. Review

Follow the method selected in Step 0:

Self-review (Default)

Aspect	Check Items
DRY	Is there any unnecessary code duplication?
Complexity	Is the approach overly complex for the intended purpose?
Specification Compliance	Does it meet the requirements in Spec.md?
Avoid Ad-hoc Solutions	Is it not an ad-hoc fix?
Security	Does it avoid anti-patterns such as those in OWASP Top 10?

Use /review Skill

Invoke the

/review

skill.

3. Check

Execute the command specified in Step 0.

Judgment Criteria:

Error → Fix and re-run
The following are allowed (but must be clearly stated in the commit message):
- Temporary failures due to mock implementation
- TDD Red state (tests written first, implementation not yet complete)
- Errors scheduled to be resolved in subsequent tasks

4. Commit