frame-intent

Shape requests into level-tagged product intents with outcomes and assumptions.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill frame-intent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frame-intent
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/product-engineering/.apm/skills/frame-intent
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill frame-intent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It turns a vague idea, request, or strategy into a structured product intent before anyone starts writing a spec, so teams can frame the right outcome instead of jumping to solutions.

Core Features & Use Cases

  • Outcome framing: Captures the steerable input, lagging outcome, and guardrail that define success.
  • Intent shaping: Works across product-vision, product-strategy, capability, and feature levels.
  • Context-aware intake: Resolves scale, maturity, knowledge-surface grounding, and assumptions for greenfield or brownfield work.
  • Use case: Use it when someone asks to shape a new feature request, convert a strategy into an intent, or prepare a brief for downstream de-risking and decomposition.

Quick Start

Ask the frame-intent skill to turn this request into a level-tagged intent with outcome, opportunity, assumptions, and decomposition.

Frequently Asked Questions about frame-intent

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

FAQPage Schema
How do I shape a vague product idea into a structured intent before writing a spec?

Shape a vague product idea into a structured intent by capturing the steerable input, lagging outcome, and guardrail that define success. This prevents jumping to solutions and frames the right outcome before writing a spec or PRD.

Can I frame a product intent for both greenfield and brownfield development contexts?

Yes, framing a product intent applies to both greenfield and brownfield contexts. It resolves scale, maturity, and structured assumptions to ensure the intake process matches the development environment before handing off.

What is the best way to convert a product strategy into an actionable request for decomposition?

The best way to convert a product strategy for decomposition is to resolve scale intake, maturity gating, and structured assumptions first. This creates a level-tagged intent with a clear outcome ready for downstream de-risking.

Do I need to define structured assumptions before preparing a product brief for de-risking?

Yes, you need to define structured assumptions before preparing a product brief for de-risking. Resolving assumptions alongside scale intake and maturity gating ensures the product intent is fully grounded before handoff.