skills.rest
zhongadamwang
zhongadamwangCOMMUNITY
Explore all skills by this author →
GitHub

goals-extract

Extract business goals, success criteria, constraints, KPIs, assumptions, and open questions from requirements into structured JSON.

1|Updated Dec 16, 2025
Search Tags:#planning#requirements#governance#KPI#traceability#goals#extract
One-click install
npx skills add https://github.com/zhongadamwang/AI_Slowcooker --skill goals-extract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: goals-extract
Source: https://github.com/zhongadamwang/AI_Slowcooker/tree/main/.github/skills/goals-extract
Command: npx skills add https://github.com/zhongadamwang/AI_Slowcooker --skill goals-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform ambiguous requirements into a structured set of strategic artifacts by extracting a clear business goal, success criteria, constraints, KPIs, assumptions, and open questions from inputs.

Core Features & Use Cases

  • Goal extraction: Derives a single goal statement from requirements input.
  • Criteria and KPI capture: Identifies success criteria, KPIs, and constraints to guide delivery.
  • Assumptions and questions: Surface assumptions and open questions to enable alignment across stakeholders.
  • Use Case: Given a product brief and backlog of user stories, generate a structured goals JSON ready for planning and traceability.

Quick Start

Use the goals-extract skill to process the requirements document and produce a structured JSON with fields: goal_statement, success_criteria, kpis, constraints, assumptions, open_questions.

Frequently Asked Questions about goals-extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract KPIs and success criteria from product briefs?▼

You can extract KPIs and success criteria from product briefs by processing the requirements document to yield a structured JSON artifact containing goal statements, constraints, and open questions for downstream planning.

What is the best way to turn user stories into actionable goals?▼

Turning user stories into actionable goals involves analyzing the requirements bundle to derive a single business goal statement, capture assumptions, and surface open questions to enable alignment across stakeholders.

Can I generate a structured goals JSON from a backlog of user stories?▼

Yes, you can generate a structured goals JSON from a product brief and backlog of user stories, producing fields like goal_statement, success_criteria, kpis, constraints, assumptions, and open_questions for planning.

Does requirements traceability work with ambiguous specification documents?▼

Requirements traceability works with ambiguous specification documents by ensuring deterministic extraction of business goals and KPIs, linking the generated structured goals artifact directly back to the source requirements.

How do I surface assumptions and open questions from requirements for stakeholder alignment?▼

To surface assumptions and open questions from requirements, you analyze the input text to identify gaps in the specification, yielding a structured artifact that enables alignment across stakeholders during delivery planning.

Related Skills

Explore More Product & Management Skills→
rafalwizenrafalwizen

maister:requirements-critic

Identify gaps and CRUD-disguised domain logic in software requirements.

Community
Intermediate
MINT-IAMINT-IA

gsd-stats

Aggregate phase, plan, requirements, git metrics, and timeline into a single dashboard.

Official
Intermediate
tmcfarlanetmcfarlane
105

technical-roadmap-planning

Produce structured multi-quarter technology roadmaps with milestones, ownership, and budgets.

Community
Advanced
normdist-ainormdist-ai

voice-of-customer

Extract actionable requirements from customer messages using Kano analysis and affinity diagrams.

Community
Advanced