Review OpenSpec change artifacts for business value, scope, and acceptance criteria.
npx skills add https://github.com/ConductionNL/decidesk --skill team-po
Please help me install this Agent Skill. Skill: team-po Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/team-po Command: npx skills add https://github.com/ConductionNL/decidesk --skill team-po
Review OpenSpec change artifacts from the perspective of a Product Owner. Validates business value, acceptance criteria quality, scope, and cross-app impact.
Load the change context from the openspec directory and begin the PO review by loading proposal.md, specs/, design.md, tasks.md, and plan.json, then evaluate according to business value, scope, and acceptance criteria.
High-intent search queries and answers about installing and using this skill.
Reviewing OpenSpec change proposals involves evaluating business value, scope boundaries, and acceptance criteria quality before code is written. Load proposal.md, specs/, design.md, tasks.md, and plan.json from the openspec directory to begin the structured PO review process.
Validating acceptance criteria requires assessing cross-app impact and dependencies to prevent scope creep. Produce a structured review report with prioritized actions that capture actionable scope boundaries and communicate cross-app implications to drive team alignment.
Checking cross-app impact involves analyzing OpenSpec delta specs and related documentation across the team workflow. Assess dependencies and communicate actionable cross-app implications to prevent misaligned deliverables and scope creep.
Yes, you can assess business value and completeness by reviewing proposals, specs, and tasks before development. Validate OpenSpec change artifacts by evaluating clarity, scope, and acceptance criteria quality to ensure alignment prior to implementation.
Refining OpenSpec change artifacts requires complete context from proposal.md, specs/, design.md, tasks.md, and plan.json. Without these inputs, accurately validating scope boundaries, capturing actionable acceptance criteria, and assessing cross-app dependencies becomes difficult.
Yes, OpenSpec documentation is required to perform a Product Owner spec review. Load change context from the openspec directory, specifically proposal.md, specs/, design.md, tasks.md, and plan.json, to evaluate business value and scope accurately.
xiayu519Create OpenSpec change proposals with proposal.md, design.md, and tasks.md artifacts.
legalopsconsultingOrchestrate local counsel engagement management across multiple jurisdictions.
johwerRefine product backlog items and sprint plans with acceptance criteria.
AGIBuildReview business goals, PRDs, user journeys, and UX designs for completeness and logic.
