Clarify vague feature requests by enforcing a formal requirements process.
npx skills add https://github.com/schmidtkk/skills --skill it-product-manager
Please help me install this Agent Skill. Skill: it-product-manager Source: https://github.com/schmidtkk/skills/tree/main/it-product-manager Command: npx skills add https://github.com/schmidtkk/skills --skill it-product-manager
Use when a user presents vague feature requests, scope creep pressure, or skips requirements gathering. Also use when defining tasks without acceptance criteria, when delivery estimates are needed too early, or when change requests arise mid-project.
Ask for explicit acceptance criteria and measurable success metrics for each task.
High-intent search queries and answers about installing and using this skill.
Clarify vague feature requests by enforcing a formal requirements process that demands explicit acceptance criteria and measurable success metrics for each task. This procedural guardrail prevents scope creep by forcing product teams to define exactly what is being built before delivery estimates.
Define tasks when acceptance criteria are missing by applying procedural guardrails that guide task definition during discovery. The process transitions modes to enforce disciplined requirements management, ensuring measurable success metrics are established before development begins.
Formal requirements management for product planning is needed during discovery, task definition, and mid-project change requests. It is essential when users present vague feature requests, skip requirements gathering, or demand delivery estimates too early without defined scope.
Handle mid-project change requests by enforcing a formal requirements process that applies procedural guardrails and mode transitions. This disciplined requirements management approach clarifies scope creep and mandates explicit acceptance criteria before approving any project changes.
Delivery estimates fail without clear task definition because vague feature requests and missing acceptance criteria obscure what is actually being built. Enforcing a formal requirements process clarifies scope and establishes measurable success metrics, enabling accurate delivery estimates.
Yes, this requirements process is designed for product teams during discovery. It enforces disciplined requirements management by specifying procedural guardrails and mode transitions that clarify vague feature requests and define task acceptance criteria.
constellizeGenerates a scope-lock.md artifact enforcing governance for constellation mapping and gap analysis.
X-School-AcademyPlan agile sprints by breaking product requirements into backlogs with acceptance criteria and test plans.
Likas07Convert project specifications into development tasks with acceptance criteria.
bychrisrManage product backlogs and user story lifecycles with automated validation and prioritization.
