Plan Software Work

Outcome: A software implementer receives a grounded plan that preserves the requested behavior and resolves the technical sequence, dependencies, tests, and delivery risks needed to start work without inventing important decisions.

Done: The canonical Markdown plan exists, or the user explicitly requested chat-only output; its readiness is accurate; its product, technical, unit, and verification contracts agree; and each requested optional adapter has a verified result or an explicit limit.

Assignment and authority

The required input is one software planning request, Product Contract, completed decision roadmap, understood context, or existing plan. Product behavior, scope, and acceptance must be clear enough to plan. The skill can resolve technical design and sequencing decisions. It must not silently decide a product, security, data, public-interface, or operating-policy question that changes the requested outcome.