backlog-add

To convert meeting notes into structured backlog items, the Skill extracts delayed or TODO-like content from your reports and transforms it into standardized fields like priority, type, effort, symptom, and plan. It then appends these validated entries into your backlog document.

Batch importing requirements from a file into a backlog is handled by parsing the document to extract TODO-like content, generating separate IDs for each item, and writing them in an ordered manner to the backlog file. The Skill requires a user confirmation preview before executing the write operation.

Yes, you can log backlog items using a direct parameter mode for fast entry. You provide the module, title, priority, type, effort, symptom, and plan, and the Skill validates these fields against allowed value constraints before generating a preview for your confirmation.

Allowed priority values for a backlog entry are P0, P1, and P2. Effort values must be S, M, L, or XL, and the type must be bug, feature, or refactor. The Skill enforces these constraints and requires strict field completeness before writing to the document.

No, the backlog creation process does not modify review documents or business code. It safely extracts information and writes only to the backlog document, ensuring your original review notes and meeting minutes remain unchanged during the structured entry generation.

A preview is required before appending items to the backlog to enforce validation and user confirmation. This guardrail ensures the extracted and transformed fields meet strict completeness and allowed value constraints, preventing incorrect or incomplete entries from being written into your document.