Decompose product requirements into dependency-aware JSON planning artifacts with acceptance criteria.
npx skills add https://github.com/gracefullight/krds --skill oma-pm-gracefullight
Please help me install this Agent Skill. Skill: oma-pm Source: https://github.com/gracefullight/krds/tree/main/.agents/skills/oma-pm Command: npx skills add https://github.com/gracefullight/krds --skill oma-pm-gracefullight
It converts ambiguous or complex product requests into actionable plans so teams can execute without guessing scope, priorities, or dependencies.
Use case: You’re given a feature request like “Add comment moderation and reporting to the blog,” and you need a plan that defines the comments/reporting APIs, orders dependent tasks correctly, and specifies acceptance checks for security and quality.
Ask the agent to produce a prioritized execution plan for your product request, including dependencies, acceptance criteria, and any needed API/data contract sketches.
High-intent search queries and answers about installing and using this skill.
To decompose product requirements, you break them into atomic tasks with clear owners, priorities, and dependency edges, while validating task atomicity and surfacing assumptions to create a dependency-aware plan.
Acceptance-criteria-first planning produces measurable, testable acceptance criteria before execution begins, ensuring downstream feature development is verifiable and scope is clearly defined from the start.
Creating a product execution plan with API contracts involves sketching data contracts upfront and embedding security, testing expectations, and risk management notes aligned with ISO 31000 governance standards.
Yes, you can align project roadmaps with ISO 21500 delivery recommendations by applying governance frameworks to dependency-aware planning artifacts tailored for ambiguous or multi-domain feature requests.
The best way to break down complex feature requests is through contract-first planning, which validates task atomicity, orders dependent tasks correctly, and outputs prioritized JSON plan artifacts for execution.
No, you do not need defined API data contracts beforehand; the planning process scaffolds API and data contracts during task decomposition while simultaneously surfacing dependencies and assumptions.
cccnam5158Convert PRDs into structured, dependency-aware task lists.
mrvladd-dVerify task completion against acceptance criteria and generate verification reports.
pkuppensVerify APIs, data schemas, and module contracts against design specifications.
ddarkrDecompose product requirements into task structures with dependencies and governance alignment.
