What to provide
Repository, stack, actors, release targets, approval rules, and Jira or Notion setup.
What you will get
Draft Markdown files, one feature contract, and a tracking map.
Copy the full prompt
Customize the bracketed fields.
Use approved business information and have a person review the result before acting.
Help prepare a repository operating kit.
Repository and stack: [details]
Team and product roles: [roles]
Release targets: [local, development, staging, production]
Approval boundaries: [rules]
Tracking tools: [Jira, Notion, or other]
Read the existing root and scoped AGENTS.md files and relevant docs before proposing changes. If access is unavailable, ask for non-sensitive excerpts. Draft Markdown content for a root AGENTS.md, a README getting-started section, and docs/contracts/[feature].md. Define the feature goal, actors, entry points, actions and results, permissions, counterpart visibility, persistence, edge states, and concrete acceptance checks. Keep technical state in Git and track operational work in Jira or Notion using stable task IDs and links to contracts, commits, reviews, and runtime evidence. Propose connector permissions and mapping fields, but do not authenticate, create tokens, connect integrations, or write external records without explicit authorization. Preserve existing policies and unrelated work. Return proposed files, validation steps, and unresolved decisions before implementation.
Response requirements:
- Begin with a short summary of the goal, confirmed facts, assumptions, and missing information.
- Ask focused clarification questions before completing the work when a missing answer would materially change the result.
- Use clear headings, tables, checklists, or numbered steps where they make the output easier to use.
- Keep source facts separate from recommendations. Quote or cite supplied evidence when the task depends on source material.
- Mark unsupported details, decisions, owners, dates, costs, credentials, and commitments as [TO CONFIRM].
- Identify the three most important risks, failure conditions, or quality checks.
- End with a practical next-action checklist that names the responsible role and the evidence needed to confirm completion.
- Include a final self-review: check the answer against this prompt, list any unmet requirement, and correct it before responding.
- Do not claim that you accessed a system, verified an external fact, completed an action, or tested the result unless evidence in this conversation proves it.Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.