Code

Plan, implement, test, and verify multi-step coding tasks.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/wewetv1987-cell/openclaw-backup --skill code-wewetv1987-cell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code
Source: https://github.com/wewetv1987-cell/openclaw-backup/tree/main/skills/code
Command: npx skills add https://github.com/wewetv1987-cell/openclaw-backup --skill code-wewetv1987-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns multi-step coding requests into a controlled workflow so implementations are planned, executed, tested, and delivered with confidence instead of guesswork.

Core Features & Use Cases

  • End-to-end implementation: Breaks larger coding requests into testable steps before any code is written.
  • Execution orchestration: Keeps work moving through planning, implementation, and verification without unnecessary pauses.
  • Quality assurance: Requires proof of correctness through tests, screenshots, or observable output before delivery.
  • Use case: Helpful when building a feature, fixing a bug, or coordinating several related changes across files while maintaining clear state.

Quick Start

Ask the Code skill to plan, implement, and verify a multi-step coding task in the current repository.

Frequently Asked Questions about Code

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

FAQPage Schema
How do I plan and verify multi-step code implementation in a single workflow?

Multi-step code implementation requires a coordinated workflow that breaks requests into testable steps before writing code. This approach orchestrates planning, execution, and verification, demanding proof of correctness through tests before delivery to avoid untested outputs.

What is the best way to ensure bug fixes are actually tested before delivery?

To ensure bug fixes are tested before delivery, use a workflow that requires validation through observable output or tests. This controlled process tracks state across files, moving fixes through implementation and verification without unverified code.

Can I coordinate feature builds across multiple files without losing track of state?

Yes, you can coordinate feature builds across multiple files by using a tracked state workflow. This orchestration manages stepwise work, ensuring each file change is planned, implemented, and verified for correctness before the overall feature is delivered.

Does end-to-end coding workflow require proof of correctness for UI updates?

End-to-end coding workflows do require proof of correctness for UI updates. This validation mechanism ensures observable output, like screenshots or tests, is verified before delivery, preventing untested UI changes from being shipped.

When should I avoid using a stepwise coding workflow?

You should avoid using a stepwise coding workflow for simple, single-step modifications that require no planning or multi-file state tracking. This orchestration is designed for complex tasks needing validation before delivery, not trivial tweaks.