spec-driven-extended-intent

Facilitates team dialogue to formulate a Daily Intent Brief before planning.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/kxnzee/multi-repo-specs --skill spec-driven-extended-intent-kxnzee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-extended-intent
Source: https://github.com/kxnzee/multi-repo-specs/tree/main/extensions/spec-driven-extended/skills/spec-driven-extended-intent
Command: npx skills add https://github.com/kxnzee/multi-repo-specs --skill spec-driven-extended-intent-kxnzee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into tasks without a shared understanding of what change they want to create, why it matters now, and how success will be measured. This Skill runs a short Socratic facilitation session that turns vague requests like "add an integration" or "do a migration" into a clear, measurable Intent before any planning begins. ## Core Features & Use Cases - Intent Classification: Categorizes the discussion into Customer Outcome, System Evolution, Compliance & Risk, or Operational Improvement, and adapts facilitation logic accordingly. - Socratic Facilitation: Asks one question at a time, offers 2-4 mutually exclusive answer options when possible, and helps resolve weak formulations without dictating decisions. - Daily Intent Brief Output: Produces a structured Russian-language brief covering the change, urgency, expected improvement, success criteria, constraints, risks, and recommended focus. - Use Case: A platform team says "we need to migrate the service." The Skill guides them to articulate what limitation disappears, what risk decreases, and how they will know the migration succeeded, then captures it in the brief. ## Quick Start Ask the agent to formulate an Intent for your change, for example: "Help me formulate an Intent for migrating our billing service to the new platform."

Frequently Asked Questions about spec-driven-extended-intent

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

FAQPage Schema
How do I write a good Intent statement before sprint planning?▼

Start by stating what change you want to create and why it matters now, then define what will improve and how success will be measured. This Skill facilitates that dialogue one question at a time and captures the result in a Daily Intent Brief.

What is a Daily Intent Brief in spec-driven development?▼

A Daily Intent Brief is a short structured document capturing the intended change, its urgency, type, expected improvement, success criteria, constraints, risks, and recommended focus. It aligns the team before planning and task breakdown begin.

Does intent facilitation work for technical or infrastructure changes?▼

Yes. The Skill classifies intents into Customer Outcome, System Evolution, Compliance & Risk, and Operational Improvement, so platform migrations, security fixes, and regulatory work are treated as valid sources of value without forcing customer-impact framing.

Can this Skill create tasks or modify project files?▼

No. It acts purely as a facilitator: it does not call other skills, commands, or subagents, does not assign tasks, and does not modify files. Its only output is the agreed Daily Intent Brief.

What happens if my team gets stuck defining the intent?▼

The Skill summarizes what has been said, proposes 2-3 alternative intent formulations, explains the differences, and lets the team pick, merge, refine, or reject them. Facilitation continues until the intent is clear enough to work from.