Skip to content

Templates

Template 1: Atomic Iteration (1–2h)

  • Objective (Feature):
  • Minimum scope: what is in / what is NOT in.
  • Baseline applied: checklist used.
  • Prompt used: link/ID.
  • Evidence: PR/commit + CI results.
  • Recovery note (if it broke): what failed, how it was fixed inside the hour, and the baseline rule added.

Template 2: Sprint Log / Evidence Timeline

  • Timestamp → Action → Result → Link (issue/prompt/commit/build)

Template 3: Baseline Folder Checklist

  • Repository structure
  • Conventions (names, folders)
  • Security (minimums)
  • Testing (minimums)
  • CI gates (minimums)
  • Explainability: can the change be described in one paragraph (3 AM test)?

Template 4: Prompt anatomy (per iteration)

  • Goal: single task the AI must achieve.
  • Context: baseline links (security, coding standards), roadmap node/persona, and constraints.
  • Quality gates: tests and metrics required to accept the output.

Template 5: 24-hour A-Dev marathon

  • Definition (15m): feature → prompt with scope.
  • Orchestration (30–45m): direct AI with baseline rules.
  • Verification (10–15m): run tests/security, no carry-over debt.
  • Integration (5m): merge + baseline update with lesson learned.

Template 6: First commit (A-Dev foundation)

  • BASELINE.md: five non-negotiables, 3 AM test, living baseline update rule, links to security/coding standards.
  • ROADMAP.md: personas, features, two-level plan mapping (roadmap → iterations), and success behaviors.
  • Prompt folder: prompt skeleton with goal/context/quality gates referencing roadmap node and baseline.

Template 7: A-Dev Foundation (pillars)

  • Effort → Baseline: list current discipline-as-code rules to avoid AI noise/debt.
  • Creativity → Persona: state the product vision and personas guiding decisions.
  • Organization → Traceability: map roadmap paths to tasks and verification.
  • Responsibility → Simple Machines: document infra choices and data isolation.
  • Result → Superagency: describe how one orchestrator covers the 1% highest-value work.

Template 8: Health check & deployment (Simple Machine)

  • Liveness: /q/health/live (expect 200), probe every 10s, failureThreshold 3.
  • Readiness: /health/ready (expect 200), probe every 10s, failureThreshold 3.
  • Ports: 8080 TCP.
  • Flags: Run behind feature toggles for Live Alpha (no staging detour).
  • Security context (non-root): drop ALL capabilities, read-only root filesystem, runAsNonRoot.
  • Resources: small requests (e.g., 50m CPU, 52Mi RAM) with burst limits (e.g., 4 CPU, 1Gi RAM) to support rampage → steady state.