to-intent

Synthesizes conversations into product INTENT.md maps or committed effort intake files.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/peachest/skills --skill to-intent-peachest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-intent
Source: https://github.com/peachest/skills/tree/main/in-progress/to-intent
Command: npx skills add https://github.com/peachest/skills --skill to-intent-peachest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Conversations about what to build evaporate when the session ends, leaving no durable record of product intent, story priorities, or why a change was requested. This Skill turns the current conversation into a persistent intent file so downstream specs, tickets, and decision maps all trace back to a stable source of truth. ## Core Features & Use Cases - Product mode: Writes or updates a repo-root INTENT.md containing the product brief, personas, user journey, and stories grouped by release with stable ids, priorities, effort estimates, and verifiable Done-when criteria. - Effort mode: Writes a committed intent/<slug>.md intake artifact for a single change, capturing Problem, Proposed outcome, Constraints, and Open questions with origin and status frontmatter. - Update passes and loop closure: Re-synthesizes an existing INTENT.md while preserving story ids, drops completed stories transparently, and retires effort files to done after verification. - Use Case: After a long planning discussion about a new CLI tool, run the Skill to produce an INTENT.md with MVP and Release 2 story cuts, then hand a sharp story off to a spec-writing workflow using its stable id. ## Quick Start Turn this conversation into an INTENT.md product map at the repository root with prioritized stories and acceptance criteria.

Frequently Asked Questions about to-intent

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

FAQPage Schema
How do I turn a planning conversation into a product requirements document?▼

Run the Skill in product mode to synthesize the conversation into an INTENT.md at the repository root. It drafts the product brief, releases, and stories with priorities and Done-when criteria, then quizzes you for approval before writing the file.

How to record the intent of a single change before implementation?▼

Use effort mode, which writes a committed intent/<slug>.md file with Problem, Proposed outcome, Constraints, and Open questions sections. The frontmatter records the origin (story id, idea, incident, diagnosis, or ticket) and a status lifecycle from draft to done.

Does the intent file stay in sync when stories are completed?▼

Yes, a later run acts as an update pass: it re-reads INTENT.md, re-synthesizes against the new conversation, keeps ids of surviving stories, and drops completed ones while telling you which. Story ids are stable forever unless a story is replaced.

What happens when a story cannot be defined verifiably?▼

A story whose Done-when cannot be sharpened into a single verifiable statement is treated as fog, not a story. It is parked in a later release at could priority or handed to a decision-mapping workflow whose tickets clear the fog first.

When should I use effort mode instead of product mode?▼

Use effort mode when the conversation concerns one change, fix, or incident response rather than the product as a whole. Product mode is the default for discussions about releases, story cuts, and priorities across the whole product.