itseffi/productize/productize-actionable-research-briefs-from-problem-statements-and

Claude Code and agent skill by itseffi/productize

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Actionable research briefs from problem statements and solutions. Use when the user needs a product workflow for user research related to actionable research briefs from problem statements and solutions. Trigger terms: user-research, research-brief, ux.

Install

npx vskill@latest install itseffi/productize/productize-actionable-research-briefs-from-problem-statements-and

SKILL.md

The same SKILL.md was published earlier as itseffi/productize/productize-actionable-research-briefs-from-problem-statements-and.

Actionable research briefs from problem statements and solutions

Productize Preamble

Before producing the artifact, implementation step, or code change, classify the work:

  • User/persona: founder, product leader, AI PM, AI builder, stakeholder, or mixed/unknown.
  • Product stage: idea, validation, PMF search, growth, scale, pivot, or unknown.
  • Artifact mode: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.
  • Artifact format: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.
  • Evidence standard: what is known, assumed, missing, and risky.
  • Decision mode: recommend, ask for a blocking input, or proceed with explicit assumptions.

Operating rules:

  1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.
  2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.
  3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.
  4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.
  5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.
  6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.
  7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.
  8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.
  9. If you must ask a blocking question, use this compact format: AskUserQuestion: <one question> Why it matters: <decision it changes>.
  10. Record completion status for durable work as completed, blocked, deferred, or needs-review when runtime hooks are available.

Artifact format policy:

  • Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.
  • Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams/tables/comparisons/screenshots, the artifact is meant to be shared, or interaction/export controls would help the user stay in the loop.
  • Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.
  • HTML artifacts must be local-first and portable: one file, embedded CSS/JS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.
  • Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy/export buttons when they improve review speed. Avoid decorative complexity that hides the decision.
  • For implementation work with ambiguities, use $implementation-notes when the user asks for a running notes file, especially implementation-notes.html or implementation-notes.md.

Runtime hooks, if available:

  • Use productize-workflow start "<user request>" at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.
  • Use productize-workflow complete --id <id> --status completed|blocked|deferred|needs-review --artifact-type <type> --summary <summary> before ending durable product work; it records the artifact, saves context, and logs completion status.
  • Use productize-update-check --strict at the start of maintenance, setup, release, or generated-output work.
  • Use productize-config to read or write user/team preferences such as persona, artifact mode, evidence threshold, or update-check policy.
  • Use productize-session-log to record important workflow decisions.
  • Use productize-artifact-log when a durable artifact is produced.
  • Use productize-context-restore before restarting long-running product work from scratch.
  • Use productize-context-save after producing a durable strategy, research, spec, or stakeholder artifact.
  • Use productize-registry-search or productize-skill-router when routing is ambiguous.
  • Use productize-completion-status to log whether the workflow completed, blocked, deferred, or needs review.

Telemetry standard:

  • Keep telemetry local by default in .productize/ or PRODUCTIZE_STATE_DIR.
  • Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.

Current skill metadata:

  • Skill: actionable-research-briefs-from-problem-statements-and
  • Lifecycle: Discover
  • Category: Discovery
  • Primary artifact: Actionable research briefs from problem statements and solutions research brief with evidence, insight clusters, assumptions, and next validation steps

Use this skill to run the Productize prompt contract for Actionable research briefs from problem statements and solutions.

Instructions

  1. Treat every {{PLACEHOLDER}} in the contract as an input to collect, infer, or mark as missing.
  2. If missing information blocks useful work, ask only for the blocking inputs. If work can proceed, state assumptions explicitly.
  3. Follow the contract's GOAL, CONSTRAINTS, FORMAT, and FAILURE clauses exactly.
  4. Preserve the required output schema unless the user explicitly asks for a different artifact.
  5. Keep claims grounded in the provided inputs and disclose gaps.

Prompt Contract

INPUTS <provided_inputs>

  • {{PROBLEM_STATEMENT}}
  • {{PROPOSED_SOLUTION}}

</provided_inputs>

GOAL Produce a high-quality deliverable for: Actionable research briefs from problem statements and solutions. Success metric:

  • Completes all required tasks and decision logic from the prompt instructions.
  • Output is specific, evidence-based, and actionable.
  • Output follows the required structure exactly.

CONSTRAINTS

  • Use only provided inputs and clearly state assumptions when information is missing.
  • Do not skip required analysis steps, sections, or validation logic.
  • Keep recommendations/outputs grounded in the input context; avoid generic filler.
  • Analyze {{PROBLEM_STATEMENT}} and {{PROPOSED_SOLUTION}} to produce an actionable UX research brief.
  • Include and connect the following components:
  • Background context.
  • Scope and key risks to investigate.
  • Rough research timeline.
  • Research type.
  • Research methods (qualitative and/or quantitative as appropriate).
  • Concrete deliverables.
  • Expected outcomes, learnings, and measurement plan.
  • Keep recommendations specific, feasible, and aligned to decision-making needs.
  • Provide rationale for chosen research type/methods/timing.

FORMAT Return exactly this structure:

<research_brief>

Introduction

[Brief summary of problem and proposed solution]

Background Context

[Context and core issues]

Scope and Risks

[What the research will cover and key risks/challenges to validate]

Rough Timelines

[Phased timeline with approximate duration]

Type of Research

[Evaluative, generative, exploratory, validation, etc., with rationale]

Research Methods

[Methods, participants, and why they fit]

Research Deliverables

[Specific outputs from the research]

Expected Outcomes, Learnings, and Measurements

[What decisions this research should inform and how success will be measured] </research_brief>

FAILURE

  • <research_brief> schema is missing, malformed, or materially incomplete.
  • Required brief components are missing or weakly specified.
  • Methods are not aligned to the problem/solution or lack clear rationale.
  • Deliverables/outcomes are generic and not decision-oriented.
  • Claims are generic or not grounded in provided inputs.
  • Assumptions are used but not explicitly stated.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/itseffi/productize/productize-actionable-research-briefs-from-problem-statements-and/badge)](https://verified-skill.com/skills/itseffi/productize/productize-actionable-research-briefs-from-problem-statements-and)

Something wrong with this skill or its page? Tell us.