code-implement

Implements method bodies and resolves TODO markers from code skeletons in dependency-ordered batches.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill code-implement-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-implement
Source: https://github.com/HACK-WU/skills/tree/main/skills/code-implement
Command: npx skills add https://github.com/HACK-WU/skills --skill code-implement-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After design-to-code generates code skeletons with contract comments, AI coding tends to be unstructured—writing code without context preparation, batching strategy, or contract verification, which causes drift from design intent and inconsistency with existing project style. ## Core Features & Use Cases - Contract-first batch implementation: Reads skeleton contract comments, code-survey results, and dependency docs before filling method bodies, processing batches in dependency DAG order. - Parallel acceleration: Dispatches order-independent batches to sub-agents via task-dispatch while serializing dependent batches, with cross-batch file conflict handling. - Contract verification: Validates implemented code against skeleton contracts across method coverage, signature consistency, exception handling, TODO resolution, and style alignment. - Use Case: After design-to-code produces skeleton files for a user service and order service, run this Skill to fill in all method bodies, resolve TODO markers in place, and verify the implementation matches every contract comment before archiving. ## Quick Start Ask the AI to start skeleton-based coding implementation using the skeleton-status.md from the latest design output.

Frequently Asked Questions about code-implement

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

FAQPage Schema
How do I implement code from skeleton files with contract comments?

Locate the skeleton-status.md from design-to-code output, read the contract comments in each skeleton file, then fill method bodies batch by batch in dependency order. Verify the implementation against contracts before finalizing.

How to parallelize coding across multiple skeleton batches?

Batches without dependencies between them can be dispatched to parallel sub-agents via task-dispatch, while dependent batches run serially. Each sub-agent receives the skeleton files, style references, and dependency docs for its assigned sub-requirement.

What happens when skeleton comments conflict with the design document?

The skeleton contract comments take precedence because they are the precise translation of the design into implementation contracts. Do not revert to the design document to correct the skeleton; escalate significant suspected errors to the user.

Can this work without code-survey or dependency-docs outputs?

Yes, missing reference documents are detected and skipped gracefully. Implementation then relies on skeleton contract comments and existing project code to infer style and external API usage, though results may be less consistent.

What are the limitations of skeleton-based code implementation?

It only fills implementations according to existing skeleton contracts and does not generate skeletons or archive results. Method signatures must not be changed during coding; contract problems require returning to the design phase.