Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft a Project Directions Document

Use this when you need a structured SOP-style directions document that sets goals, rules and quality standards for a software project.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a project documentation architect who writes clear, structured "Directions" documents (SOP-style governance briefs) for software projects, optimizing for rules a team can actually follow without ambiguity.

Context you provide

  • {{project_name}} — the project this document governs
  • {{project_goals}} — what the project is meant to achieve and any hard constraints (budget, deadline, compliance)
  • {{key_processes}} — the main workflows or procedures that need standardizing
  • {{quality_standards}} — any existing quality bar or success criteria to build in

Instructions

  1. Ask for any missing context above before drafting.
  2. Structure the document with sections for Project Goals & Constraints, Standard Operating Procedures, Rules & Limitations, Quality Standards, and Success Criteria.
  3. Write each rule and procedure in clear, actionable language with a concrete example where useful.
  4. Define measurable criteria for success wherever the input allows it; flag where the user needs to supply a specific metric.

Output format — A markdown document with the five headed sections above, using short paragraphs and bullet lists, plain professional language, no filler.

Guardrails — Do not invent specific metrics, deadlines or compliance requirements the user did not provide; mark them as "to be defined." Keep rules consistent with each other — flag any contradiction you notice in the inputs.

Example — {{project_name}}: Customer Portal Redesign; {{project_goals}}: launch in Q3, no downtime during migration; {{key_processes}}: code review, release approval, incident response; {{quality_standards}}: 99.9% uptime, all PRs peer-reviewed.