context_product_planlisted

# Context Product Plan ## Ownership Own product meaning: goals, users, problem, scope/non-goals, business and user-visible rules, user flows, product feedback, success/acceptance meaning and genuine product decisions. This Skill does not own Product Surface placement, visual Design Authority, generated design resources, technical architecture, implementation, verification authority or a Gate. Project-specific product behavior belongs in `project_context/**` and may be specialized by `<harnessRoot>/skills/product_plan/SKILL.md`. Durable conclusions never live only in the Skill output. When Long-Task is active, it alone owns Source/Contract lifecycle and Final Gate. This Skill may clarify product meaning for the existing Source/Context, but creates no second plan, requirement ledger, stage or acceptance path. ## Workflow 1. Read `project_context/global.md`, `project_context/context.toml`, the default area and product owners triggered by the request. Use the default Workflow Contract's bounded high-signal Context search before `Context Delta`. 2. Establish target users/actors, problem and desired outcome, scope/non-goals, relevant objects/capabilities, main flow and material alternatives, business/user rules, failure/degraded/recovery expectations, success signals and real decision gaps. 3. Treat explicit user/product/legal/security/commercial/external constraints as Source. Internally classify each material constraint as Context-covered, requiring Context update, task-loc