Skip to content

Add implementation_bug entry type to recap #383

@acreeger

Description

@acreeger

Summary

Add a new recap entry type implementation_bug to capture when completed implementation is discovered to not work fully or breaks something else. This represents the discovery of the problem post-implementation.

Use Cases

  • Tests fail after implementation is "complete"
  • Build breaks when running validation
  • Runtime error discovered during testing
  • Existing functionality regressed
  • User reports the implementation doesn't work as expected

Schema Change

Add to entry types:

type: z.enum(['decision', 'insight', 'risk', 'assumption', 'implementation_bug', 'other'])

Example entry:

{
  "id": "uuid",
  "timestamp": "2025-12-16T14:30:00Z",
  "type": "implementation_bug",
  "content": "Auth flow broken after implementation - session token not preserved during redirect"
}

Prompt Guidance

Add to recap guidance:

  • implementation_bug: Discovery that completed implementation doesn't work fully or breaks something else - NOT the fix, just the problem found

Distinction

  • risk = anticipated problem (before implementation)
  • implementation_bug = discovered problem (after implementation thought complete)

This captures: "we thought we were done, but it's broken"

Related

  • VS Code display: iloom-ai/iloom-vscode#65
  • Part of Loom Context Panel feature set

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions