tlc-spec-driven

To maintain traceability, specify features with traceable IDs like FEAT-01, break work into granular tasks, and execute changes with atomic commits. This enforces a clear link from initial requirements through to final code execution.

The best way to plan small changes is using a quick mode that auto-sizes rigor to fit the feature scope. This approach reduces project management ceremony and skips complex design phases when they are unnecessary for the task.

To break down architecture specifications, map existing codebases, specify features, design only for complex cases, and decompose work into granular tasks. This ensures each task is executable and validated per outcome.

Yes, you can keep persistent memory of project tasks and execution across multiple coding sessions. This maintains continuity by retaining task breakdowns and specification states between different development periods.

You should not use a full design phase when working on small software changes or minor features. By applying adaptive depth, you can utilize quick mode to skip architecture design and reduce ceremony for simpler scopes.