/write

Rule

The <execute name="main">ARGUMENTS</execute> is entry point for this command.

Skills Rubric

To select skills for implementing the feature, consider the following rubric:

Skill	When to use
coding:clean-architecture	No docs/architecture.md exists or the feature requires significant structural changes.
coding:domain-modeling	The feature is related to business logic or domain entities.
coding:principles	Fully new feature no existing code, following principles is essential.
coding:design-patterns	The feature needs changes multiple components that can benefit from design patterns.
coding:refactoring	Need to change existing code to accommodate the new feature.
coding:testing	Each new feature or behavior change requires apply testing.
coding:schema	The feature involves database changes, API contracts, or data serialization.
coding:security	The feature handles user input, auth, secrets, or crosses trust boundaries.

The language-specific skills not listed, check all available skills before deciding skills to use.

Definition

Fast overview of the feature to implement, use keyword search to find relevant information in the codebase. 1. read the specification of the feature, e.g. SPEC.md, issue tracker, project management tool 2. use lightweight sub-agents to review codebase to understand current implementation related to the feature 3. use `git log` to get context of recent changes related to the feature summary of the feature and current codebase context According to the feature requirements, determine which skills are needed and activate them. 1. discover available skills from system-reminder 2. analyze the overview with rubric of available skills 3. select the skills that are most relevant to the feature implementation 4. use Skill($skill) to activate and load its knowledge list of activated skills with their knowledge loaded Investigate the correct usage by checking official documentation for the libraries or APIs involved. 1. identify the specific library/API whose usage needs confirmation 2. use WebSearch to check the official documentation for the current API signatures and standard usage 3. confirm the officially recommended implementation approach confirmed usage patterns based on official documentation Create an implementation plan for the feature using the active skills. 1. review the feature requirements and create integration test cases to verify components work together 2. add unit test cases for edge cases and complex logic if necessary 3. depend on the test cases, break down the implementation into smaller tasks 4. break down the implementation into smaller tasks 5. for each task, determine which active skill to apply 6. sequence the tasks outside-in: start from user-facing layers (controllers, presenters, API endpoints), then work inward to use cases, and finally to entities and infrastructure — defer schema and storage decisions until the domain model shape is clear from use case needs implementation plan for the feature Execute a single task from the plan using TDD approach. 1. write failing test for the task (Red) — if you feel the urge to verify language/API behavior with `node -e` / `ruby -e` / `python -c` before writing code, that urge is telling you to add a test case for that assumption instead; see `coding:testing` Verification Discipline 2. implement minimum code to pass the test (Green) 3. refactor the code while keeping tests passing (Refactor) 4. implement the task directly 5. refactor if necessary 6. invoke the skill to verify completion rubric completed task with skill verification result Generate implementation quality report using active skills' completion rubrics. 1. for each active skill, invoke skill to verify completion rubric against implementation 2. collect all verification results and identify gaps 3. summarize overall implementation quality implementation quality report with skill-based verification 1. 2. use ask question tool to clarify scope of the feature 3. 4. 5. deeply understand the project codebase related to the feature, stay within project boundaries and do not read library or framework source code 6. enter the plan mode 7. 8. review and finalize the implementation plan for minimal change instead of over-engineering 9. refine the plan to avoid over-engineering 10. exit plan mode and wait for user confirmation 11. create tasks from the plan using TaskCreate tool, so progress can be tracked 12. 13. collect task result for quality report and update task status 14. 15. ask user if they want to commit the changes 16. suggest running `/review` to check style consistency, test quality, and architecture alignment implementation quality report

Task

$ARGUMENTS