Create an Agent Instruction File
Create a versioned Markdown instruction file under the repository’s agent or instructions directory. Define its scope, intended document type, output folder, and filename convention.
Encode a compact document standard in a repository instruction file, invoke it with a specific brief, and improve the reusable instructions from the rendered output rather than rewriting every document by hand.
Download the skill for this workflow. Version 1.0.1.


with Claire Vo
Claire creates a reusable PRD instruction file in Cursor, narrows it for a functional solo-project format, invokes it to write a neighborhood task-scheduler PRD, and checks the Markdown in her hub.
A reusable instruction file that produces concise, consistent Markdown documents in the correct directory without inventing product facts or overwriting existing work.
AI-first code editor
Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.
4 steps
Create a versioned Markdown instruction file under the repository’s agent or instructions directory. Define its scope, intended document type, output folder, and filename convention.
Ask Cursor to populate it with a compact template, section rules, evidence and assumption handling, length guidance, and a pre-write collision check.
Fill this instruction file for generating concise PRDs in @docs. Require: problem, target user, evidence, goals and measures, user journey, functional requirements, non-goals, constraints, technical notes, decisions, assumptions, open questions, and acceptance criteria. Do not invent facts. Use a slug filename, check for collisions, and report the output path. Keep the instruction file maintainable and under [limit].
Invoke the instruction file from a new prompt and provide only the product-specific brief, evidence, and constraints. Ask the agent to label missing information instead of guessing.
Using @agents/prd.md, write a PRD for [product]. User: [user]. Problem evidence: [evidence]. Core journey: [journey]. Constraints: [constraints]. Known decisions: [decisions]. Save it under @docs and do not overwrite an existing file.
Open the generated Markdown in the app and inspect structure, length, assumptions, requirements, and rendering. Correct the document, then update the instruction file when the correction should apply to future PRDs.
Turn an idea into a PRD, user stories, and a plan.
How to recover when the loop fails and where human judgment helps.

Create a repository-based system to provide an AI assistant with durable context about your team, projects, and communication channels. This enables it to perform routine tasks like summarizing daily updates and identifying stakeholders, acting as a personalized chief of staff.

Use Meta's Muse to generate a printable, multi-page family newspaper that includes a weekly schedule, weather forecasts, and activity ideas. This workflow leverages Muse's strength in creating visually appealing, family-oriented artifacts.

Coordinate agents in Slack and Cursor to propose growth experiments for human review. Ezra’s Auto XP system was still being developed at the time of the episode.
Join 250,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.