Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence without implementing Avalonia UI. Use only in an explicit WinForms-to- Avalonia migration when behavior is undocumented or the orchestrator routes here. Generated artifacts must use the current repository's real paths, terminology, and capabilities.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Turn a WinForms app into documented contracts so the rewrite does not depend on copying event handlers. Prefer Designer metadata, resources, handlers, helpers, services, and tests over screenshots alone.
Read contract templates when writing behavior contracts, coverage matrix when checking file ownership, and module split when defining responsibility boundaries.
Classify legacy files:
| Category | Typical contents |
|---|---|
| Entry / shell | Program, main Form, startup args, runtime checks |
| Domain models | Entities and value objects mutated by legacy workflows |
| Application behavior | Use cases, policies, validation, calculations |
| State and data | In-memory state, persistence, mapping, synchronization |
| External boundaries | Filesystem, network, process, device, or service integrations actually present |
| Supporting UI | Secondary windows, dialogs, notifications, settings surfaces |
| Platform | Environment-specific capabilities and lifecycle behavior |
| Build / distribution | Projects, packaging, CI, deployment assets |
| Tests / fixtures | Unit, integration, UI tests, representative scenarios |
Assign every production file a primary module.
Suggested shape (rename to the product):
Each module doc: purpose, rewrite boundary, reviewed files, behaviors, UI coupling to strip,
risks/decisions. See references/module-split.md.
For every user-visible action:
Also list semantic window state (context, selection, modes, pending changes, status) rather than only control names.
| File | Primary module | Referenced | Notes |
Mechanically verify against a full legacy file listing.
For each major workflow: success, validation failure, cancellation, dependency failure, and recovery from partial or stale state. Derive scenarios from the application, not this skill.
Plan a stable fixture/scenario layout. Prefer the smallest representative data that exercises real behavior over inventory-only checks.
Supported platforms, accessibility expectations, hidden gesture policy, deployment strategy, external dependencies, compatibility obligations, and known bugs to preserve or fix.
Map modules to implementable capabilities ordered by dependency:
Document parallel lanes and shared-contract locks.
Load wfa-extract-domain. Do not implement Avalonia Views here.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
The English summary is being prepared. Showing the original description.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
The English summary is being prepared. Showing the original description.
Archive multiple completed changes at once. Use when archiving several parallel changes.
The English summary is being prepared. Showing the original description.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
The English summary is being prepared. Showing the original description.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
The English summary is being prepared. Showing the original description.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
The English summary is being prepared. Showing the original description.