feat-dev
Feature Development Workflow
Use this workflow when implementing a feature in qwen-code that needs design, behavioral validation, or coordinated changes across multiple files. Each phase produces a concrete artifact. Do not combine phases; the output of each phase feeds the next.
Artifact Paths
Use .qwen/ paths for planning artifacts:
.qwen/design/<feature>.md.qwen/e2e-tests/<feature>.md
Phase 1: Investigate
Understand the requested behavior and the current qwen-code implementation.
Use a code exploration agent when available. Ask it to inspect the relevant
More from qwenlm/qwen-code
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies
6docs-audit-and-refresh
Audit the repository's docs/ content against the current codebase,
6docs-update-from-diff
Review local code changes with git diff and update the official
5e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including
4qwen-code-claw
Use Qwen Code as a Code Agent for code understanding, project
4structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this
3