This repository is a small, intentionally minimal Python template you can use as the starting point for new repos.
It’s designed to be a quick workflow to get started while keeping the day-0 developer experience solid (devcontainer support, modern dependency management, and a place for agent instructions).
- Python 3.12 devcontainer setup
uvfor dependency management (pyproject.toml+uv.lock)- A tiny runnable entrypoint (
src/app.py) that loads environment variables from.envviapython-dotenv AGENTS.mdfor coding-agent guidance
Typical workflow:
- Create a new repository from this template (GitHub: “Use this template”).
- Update project metadata in
pyproject.toml(name/description). - Replace the sample app code under
src/with your real project. - Update
AGENTS.mdand this README to reflect the new repo’s purpose.
This repo uses uv.
curl -LsSf https://astral.sh/uv/install.sh | sh
uv syncuv run python src/app.pyThis template includes ruff.
uv sync --group dev
uv run ruff check .
uv run ruff format .- Copy
.env-sampleto.envand fill in values as needed. .envis gitignored.
cp .env-sample .envThis template includes an .agent/ directory containing reusable prompt “commands” and standards you can use with GitHub Copilot (and other coding agents).
.agent/commands/: ready-to-run prompts for common tasks, for example:setup/: repo bootstrap tasks (e.g. creatingAGENTS.md)project/: planning prompts (e.g. sprint planning)docs/: documentation prompts (e.g. creating ADRs)
.agent/standards/: templates and standards for consistent artifacts (ADRs, feature specs, task plans).agent/instructions/: “apply-to” instructions that guide how agents write certain file types (e.g. Bash and Bicep)
If you base a new repository on this template, treat .agent/ as a starting library: keep what helps your team, remove what doesn’t, and add org-specific workflows over time.
The devcontainer includes GitHub Copilot CLI via the official devcontainer feature (ghcr.io/devcontainers/features/copilot-cli:latest).
This template includes an enhanced Spec-Driven Development (SDD) workflow in .agent/commands/sdd/. The SDD workflow provides a structured, 9-step process for developing features with built-in quality gates and testing integration.
| Step | Prompt File | Purpose |
|---|---|---|
| 0 | sdd.0-initialize.prompt.md |
Initialize environment and verify prerequisites |
| 1 | sdd.1-create-feature-spec.prompt.md |
Create feature specification via guided Q&A |
| 2 | sdd.2-review-spec.prompt.md |
Review spec for completeness (quality gate) |
| 3 | sdd.3-research-feature.prompt.md |
Research implementation approach |
| 4 | sdd.4-determine-test-strategy.prompt.md |
Determine TDD vs Code-First approach |
| 5 | sdd.5-task-planner-for-feature.prompt.md |
Create implementation plan with test phases |
| 6 | sdd.6-review-plan.prompt.md |
Review plan for readiness (quality gate) |
| 7 | sdd.7-task-implementer-for-feature.prompt.md |
Execute implementation systematically |
| 8 | sdd.8-post-implementation-review.prompt.md |
Final validation before completion |
- Initialize: Run
sdd.0-initialize.prompt.mdto set up the environment - Start a feature: Run
sdd.1-create-feature-spec.prompt.mdwith your feature idea - Follow handoffs: Each step tells you which step to run next
- Don't skip review gates: Steps 2, 4, 6, and 8 catch issues early
- Quality gates at review steps with explicit PASS/FAIL validation
- Deterministic test strategy using a scoring-based decision matrix
- Integrated testing with mandatory test phases in implementation plans
- State management for session continuity across steps
- Artifact tracking in
.agent-tracking/directory
For full documentation, see .agent/commands/sdd/README.md.