Sample templates & prompts
Ready-to-use examples to help you configure Dev Forge for your team. Copy any template or prompt rule below and adapt it to your workflow.
Sample task templates
Templates define the structure of a generated GitHub task. Each template is a named set of sections that the AI fills in based on your raw notes.
UI Bug
Use for visual defects, broken layouts, or interaction problems in the front end.
Backend Task
Use for API changes, service refactors, or infrastructure work with clear acceptance criteria.
Feature Request
Use for new product capabilities described from a business or user perspective.
Performance Task
Use when slow queries, high memory usage, or unacceptable response times need investigation.
Security & Compliance
Use for vulnerabilities, data-protection gaps, or regulatory compliance requirements.
Documentation & DX
Use for missing or outdated documentation, onboarding gaps, or developer experience improvements.
Sample prompt rules
Prompt rules control how the AI model interprets your notes and which extra detail it adds. Combine a template with a prompt rule to tailor the output for your team's style.
Base formatter
The default prompt rule for most teams. Converts raw developer notes into a clean, concise GitHub task. No speculative requirements, no padding — just structured output that matches the selected template sections.
Copilot enhancer
Extends the base formatter with additional sections optimised for GitHub Copilot: edge cases, affected files/components, and implementation hints. Ideal for teams where Copilot Workspace or Copilot coding agent picks up tasks directly.
Strict enterprise mode
Enforces formal language, numbered requirements, and explicit traceability fields. Avoids any speculative language or implementation suggestions. Suitable for regulated industries or teams with a formal change management process.
Multilingual output
Accepts notes written in any language and always produces tasks in a single target language. Useful for distributed teams where developers write notes in their native language but the backlog must remain in English (or another standard language).
Tips for great templates & prompts
Follow these guidelines to get the most consistent results from Dev Forge.
Keep sections focused
Each template section should capture one distinct piece of information. Avoid combining "problem" and "solution" into a single section — the AI works better with clear, separated concerns.
3–6 sections per template
Templates with fewer than 3 sections produce shallow tasks. More than 6 sections risk generating padded content when the raw note is brief. Aim for 4–5 sections for everyday task types.
Pair templates with prompt rules
Assign a default prompt rule to each template to lock in a consistent style. For example, always pair the UI Bug template with Base formatter and Feature Request with Copilot enhancer.
Avoid vague instructions
Prompt rule instructions like "be helpful" or "write clearly" are too broad. Use explicit constraints: "do not suggest implementation approaches", "always include numbered acceptance criteria", "output only English regardless of input language".
Test with real notes
Before setting a template or prompt rule as active, generate 3–5 tasks using real raw notes from your team. Review the output for accuracy, completeness, and tone — then adjust the instructions as needed.
Use one default prompt rule
Mark exactly one prompt rule as the default. This rule is pre-selected in the Composer and used as the fallback when a template does not specify its own rule. Additional rules remain available for manual selection.
Ready to set up your first template?
Sign in to Dev Forge and create your templates, prompt rules and repo routing in minutes.