Prompt Sync.instructions
--- description: "Use when editing any file in prompts/ — especially burndown-chart.prompt.md, throughput-forecast.prompt.md, sprint-analysis.prompt.md, retro-input.prompt.md, stakeholder-update.prompt.md, or setup.agent.md. Ensures that changes to individual prompts are always reflected in the setup agent template, and vice versa." applyTo: "prompts/**" --- # Prompt ↔ Setup Agent Sync Rule `prompts/setup.agent.md` enthält in Step 3 eingebettete **Templates** für alle fünf generierten Prompts. Diese Templates müssen immer mit den Originalprompts in `prompts/` übereinstimmen. ## Pflicht bei jeder Änderung **Wenn `prompts/<name>.prompt.md` geändert wird:** Prüfe, ob das entsprechende Template in `prompts/setup.agent.md` (unter `### File N — .github/prompts/<name>.prompt.md`) dieselbe Änderung benötigt. Wenn ja, passe das Template an. **Wenn `prompts/setup.agent.md` geändert wird:** Prüfe, ob die Änderung eine Logik betrifft, die auch im Original-Prompt `prompts/<name>.prompt.md` vorhanden ist. Wenn ja, passe den Original-Prompt an. ## Mapping: Original → Template in setup.agent.md | Original-Datei | Template-Abschnitt in setup.agent.md | |---|---| | `prompts/sprint-analysis.prompt.md` | `### File 1 — .github/prompts/sprint-analysis.prompt.md` | | `prompts/retro-input.prompt.md` | `### File 2 — .github/prompts/retro-input.prompt.md` | | `prompts/throughput-forecast.prompt.md` | `### File 3 — .github/prompts/throughput-forecast.prompt.md` | | `prompts/burndown-chart.prompt.md` | `### File 4 — .github/prompts/burndown-chart.prompt.md` | | `prompts/stakeholder-update.prompt.md` | `### File 5 — .github/prompts/stakeholder-update.prompt.md` | ## Was synchronisiert werden muss - Schritte und Schritt-Logik (z. B. "Fetch server-side", "three sprint boundary cases") - Fallback-Regeln und Fehlerfälle (z. B. "ask user if dates cannot be read") - "Before You Begin"-Abschnitte - Hinweise und Limitations - Frontmatter `name` und `description` ## Was NICHT synchronisiert werden muss Templates in `setup.agent.md` verwenden `{placeholders}` wie `{owner/repo}`, `{label_value}`, `{sprint_scope_selection_instructions}`. Die Original-Prompts formulieren dieselbe Logik generisch. Die Placeholder-Syntax selbst muss nicht identisch sein.
fill the variables
This prompt has 4 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{placeholders}{owner/repo}{label_value}{sprint_scope_selection_instructions}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo Flow2CHQ/copilot-agile-metrics (NOASSERTION). A "Prompt Sync.instructions" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
Flow2CHQ/copilot-agile-metrics · NOASSERTION
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar