A curated, prompt‑first set of developer‑facing guides for running enterprise SDLC tasks with Amp. These guides provide generalized templates that should be adapted to your specific repository and project context. They are repository‑agnostic, assume your repo contains an AGENTS.md with team conventions, and Amp selects tools automatically and returns synthesized results only.

• Consistent structure: Why this phase matters, Pre‑flight checklist, numbered sections with "Prompt (single message)" + "What you’ll get", Exit criteria, Quick reference, Closing note.
• Prompt‑first: natural‑language prompts; no repository paths (Amp infers the current workspace).
• Enterprise‑ready: oriented for monorepos, multiple services, manifests, CI/CD, and compliance.

• Orchestrate end‑to‑end: orchestrate-chain-end-to-end-workflows-guide.md

• discover/
  • discover-explore-codebase-and-history.md
  • discover-search-documentation-guide.md
  • discover-onboard-and-learn-guide.md
• design/
  • design-plan-project-guide.md
  • design-develop-tech-specs-guide.md
  • design-define-architecture-guide.md
• build/
  • build-implement-code-guide.md
  • build-write-and-execute-tests-guide.md
  • build-create-commits-and-prs-guide.md
• deploy/
  • deploy-automate-ci-cd-guide.md
  • deploy-configure-environments-guide.md
  • deploy-manage-deployments-guide.md
• support-and-scale/
  • support-and-scale-debug-errors-guide.md
  • support-and-scale-large-scale-refactor-guide.md
  • support-and-scale-monitor-usage-and-performance-guide.md

1. Open the orchestrator guide and frame your mission with goals, scope, and success metrics.
2. Follow the phase guide(s) relevant to your task; adapt prompts to your repository context and paste as "single messages" and iterate.
3. Keep artifacts (maps, specs, tests, plans) in‑repo; link them in your PRs/issues.
4. Share your Amp thread with reviewers when useful; avoid pasting raw logs.

• Follow the shared format (Why, Pre‑flight, numbered sections with Prompt/What you’ll get, Exit criteria, Quick reference, Closing note).
• Use kebab‑case filenames; place guides in the appropriate phase subfolder.
• Keep links relative; update the orchestrator guide when adding/removing guides.
• Prompts must be repository‑agnostic; no explicit tool names, APIs, or tool‑call JSON.
• Optional Git/CLI commands are only for developer‑run verification, not Amp output.

• Amp infers repository context from your IDE/CLI; prompts never include repo paths.
• Amp chooses tools automatically and surfaces synthesized results only.