Generate a structured Intent Document with goals, constraints, and original user input.
npx skills add https://github.com/saajunaid/junai --skill intent-writer
Please help me install this Agent Skill. Skill: intent-writer Source: https://github.com/saajunaid/junai/tree/main/.github/skills/workflow/intent-writer Command: npx skills add https://github.com/saajunaid/junai --skill intent-writer
Create an Intent Document — a structured, immutable artifact that captures the user's original intent for a feature or task. This document is the anchor that prevents intent drift as work passes through the agent pipeline (PRD → Architect → Plan → Implement).
Provide a vague idea or backlog item and let the Skill generate the initial Intent Document.
High-intent search queries and answers about installing and using this skill.
To preserve user intent across an agent pipeline, you create a structured Intent Document that anchors the original goal, success criteria, and constraints before handing work to downstream agents like PRD or Architect.
An Intent Document is an immutable artifact used in backlog management to capture the original user input and provide a clear trace for amendments, preventing intent drift when pulling backlog items into active work.
To prevent intent drift when refining vague ideas before a PRD agent, generate a formal artifact containing the goal, out-of-scope items, and feasibility notes to serve as a single source of truth for downstream agents.
Yes, you can document amendments by preserving the Original User Input field within the Intent Document, ensuring a clear trace through the chain while maintaining a standardized structure for any changes.
You need a structured format like an Intent Document to pull backlog items into active work, as it generates a chain_id and feasibility notes that guide the implementation phase with a single source of truth.
You should not use an Intent Document when the original user input is already highly detailed or when the workflow bypasses agent pipelines, as the artifact is specifically designed to prevent intent drift across structured handoffs.
SakshamKandelConvert vague intent into executable specs through a five-phase workflow.
Sridhar-RanganaboinaGenerate clarifying questions and a pyramid-structured PRD from feature request context.
brabos-aiUpdate CLAUDE.md documentation to reflect current codebase architecture.
14790897Generate structured product requirement documents from unstructured problem statements.
