xp

Reconstruct user needs into experience specifications with Actor, Surface, Planes, and Invariants.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/malakhov-dmitrii/local-marketplace --skill xp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xp
Source: https://github.com/malakhov-dmitrii/local-marketplace/tree/main/plugins/beast/skills/xp
Command: npx skills add https://github.com/malakhov-dmitrii/local-marketplace --skill xp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconstructs real user needs from brief signals to produce precise experience specifications.

Core Features & Use Cases

  • Experience spec drafting: creates a structured artifact describing Actor, Surface, Planes, and Invariants that guide development.
  • Divergence handling: surfaces discrepancies between literal brief and intended outcomes, enabling safe handoffs to forge.
  • Owner signals alignment: uses OWNER.md and project context to ground decisions and validation steps.
  • Workflow integration: pairs with /forge to produce final implementation plans or stand-alone experience specs.

Quick Start

Invoke /xp <task> to generate the experience specification and divergence artifacts.

Frequently Asked Questions about xp

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

FAQPage Schema
How do I turn a brief into a structured experience specification?

To turn a brief into an experience specification, this Skill reconstructs real user needs from brief signals to produce a structured artifact describing Actor, Surface, Planes, and Invariants that guide development.

What is the best way to handle divergences between a literal brief and intended outcomes?

Handling divergences between literal briefs and intended outcomes involves surfacing discrepancies as distinct artifacts, enabling safe handoffs to downstream implementation workflows without losing the owner's original intent.

How do I align experience specs with owner signals and project context?

Aligning experience specs with owner signals uses an OWNER.md file and project context to ground decisions and validation steps, ensuring the reconstructed user needs match the project owner's intended outcomes.

Can I use this experience spec drafting Skill stand-alone or do I need a workflow pipeline?

You can use this experience spec drafting Skill stand-alone to generate specifications, or integrate it with a forge workflow pipeline to hand off final plans and maintain alignment with owner signals.

When should I not use automated experience spec drafting for my design briefs?

You should avoid automated experience spec drafting when a brief lacks clear actor definitions or project context, as the Skill relies on these brief signals to accurately reconstruct real user needs and surface divergences.