Project Spec.instructions
---
name: Project Spec Maintenance
description: Keep project-spec concise, accurate, and decision-aligned
applyTo: "project-spec/**/*.md"
---
# Project Spec Maintenance Instructions
## Source of truth discipline
- Keep project-specific facts in `project-spec/` only.
- If a requirement is unknown, keep `_TBD_` and add it to `project-spec/todos.md`.
- Do not invent requirements to fill gaps.
## Decision consistency
- Reflect accepted decisions in relevant files.
- If a decision changes, update the decision file status and affected sections.
- Avoid duplicating contradictory guidance across files.
## Scope and clarity
- Keep entries concrete and implementation-relevant.
- Mark non-applicable sections as `N/A`.
- Prefer short bullets over long narrative text.when to use it
Community prompt sourced from the open-source GitHub repo jhchein/copilot-agent-modes (MIT). A "Project Spec.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
jhchein/copilot-agent-modes · MIT
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