Skip to content

[YYYY-MM-DD] [Feature Name / Task ID]

Task Metadata

  • 📆 Date: YYYY-MM-DD
  • 🚥 Status: Draft | Plan Approved | Ready for Review | Complete

Objective

Goal: What are we trying to achieve?

  • Trigger: Why now? (User request, bug report, strategic goal)
  • Constraints: (Hard limitations)

Technical Strategy

How will we implement this?

  • Key Decisions:
    • Example: Using Library X instead of Y because...

Testing Strategy

  • Must Test: (Critical logic, complex interactions)
  • Skip: (UI styling, trivial code)

Risk Analysis

  • Potential Regressions: ...
  • Security Implications: ...
  • Files to Modify:
    • docs/architecture/...
    • src/components/...

1. Component/Function: Description

  • File: path/to/file.tsx
  • Intent: Short description of the critical logic/styling change.
// path/to/file.tsx
const example = () => {
  // Critical logic here
};

Critique & Gaps

  • Critique 1: ...
  • Critique 2: ...

Gap Analysis

  • Gap: ...

1. Hardening Item: Description

Describe a concrete improvement made after critique (reliability, security, cost, operability, etc.).

# Optional: include a focused snippet, config fragment, or command

2. Safeguard: Description

Capture an explicit safeguard added to prevent regressions or production risk.

Execution Plan

Stop: User Approval Required

Do not proceed with execution until the user has explicitly approved the Approach and Execution Plan above.

  • Step 1: ...
  • Step 2: ...
  • Verify: ...

Execution Notes

Infrastructure & Structural Hardening

  • Record implementation discoveries, deployment fixes, or structural updates made during execution.

Architecture Refinement (Optional)

  • Capture architecture changes that improved correctness, performance, or maintainability.
  • Include rationale and tradeoffs for each refinement.

Operational Rationale (Optional)

  • Document why this design is appropriate for the current project scale and constraints.
  • Briefly list alternatives considered and why they were rejected.

Deviation from Plan (Optional)

  • Deviation: What changed from the approved plan?
  • Reason: Why was the change necessary?
  • Impact: Scope, risk, or timeline impact.

User Approval & Key Learnings

Key Learnings

  • (List items here)

(User to confirm approval and add notes/learnings)

Context Memory (AI-Only)

Summary for Future Context

(Auto-generated summary of what was changed, why, and what is next.)