block

Project blocker tracking is done by parsing input for project and description, then creating a note at blockers/{project}/{date}-{slug}.md with flags for severity, owner, and due date. This ensures every blocker is systematically recorded and easy to monitor.

To prevent duplicate blockers, the system performs a duplicate check before creating a new note. It verifies existing entries in the blockers index and rewrites references to maintain a central, conflict-free log of project issues.

Updating an existing blocker's due date and severity is done by running the command with the project name, description, and new flags. The system checks for duplicates and updates the note while maintaining reference integrity in the blockers index.

Yes, you can use this for task-tracking without external dependencies. The Skill operates independently with no required dependencies, parsing input directly to create and manage blocker notes in your project repository.

Blocker notes are structured as markdown files saved at blockers/{project}/{date}-{slug}.md. The system parses your input to extract the project name, description, and flags, formatting them into a standardized note for tracking.