skills.rest
5hdaniel
5hdanielCOMMUNITY
Explore all skills by this author →
GitHub

issue-log

Documents issues, blockers, and workarounds using a structured template and severity labels.

Updated Oct 24, 2025
Search Tags:#templates#documentation#blockers#handoff#issue#severity#workarounds
One-click install
npx skills add https://github.com/5hdaniel/Mad --skill issue-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-log
Source: https://github.com/5hdaniel/Mad/tree/main/.claude/skills/issue-log
Command: npx skills add https://github.com/5hdaniel/Mad --skill issue-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document issues, blockers, and workarounds to ensure clear and reliable handoffs and task closure.

Core Features & Use Cases

  • Issue Entry Template: Provides a standard structured format for logging issues.
  • Where to Document: Guidance for Handoff Messages, per-task logs, and sprint summaries.
  • Severity & Logging: Standardizes severity labeling and keeps a persistent Issues Log for traceability.

Quick Start

Document the issue using the provided Issue Entry Template and add it to the task file under the Issues Log.

Frequently Asked Questions about issue-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document issues and blockers for a project handoff?▼

To document issues for a project handoff, use a structured Issue Entry Template to log the problem, blockers, and workarounds, then add the entry to a persistent Issues Log within the task file for clear traceability.

What is the best way to log issue severity in sprint closures?▼

Logging issue severity in sprint closures requires a standardized labeling approach within your issue documentation, ensuring each blocker and its workaround are categorized consistently in the persistent Issues Log for reliable task closure.

When do I need to use a structured issue entry template?▼

You need a structured issue entry template during handoffs, sprint closures, and per-task documentation to enforce consistent recording of blockers, workarounds, and severity labels across project-management workflows.

Where should I record workarounds and blockers during task documentation?▼

Record workarounds and blockers in the Issues Log section of your task file, using the standardized entry template to ensure documentation is maintained in handoff messages and sprint summaries.

Does standardizing issue logging improve handoff communication?▼

Standardizing issue logging improves handoff communication by enforcing a consistent format for documenting blockers, workarounds, and severity, which ensures all context is transferred reliably during sprint closures and task transitions.

Can I use this issue documentation approach for per-task logs?▼

Yes, you can apply this issue documentation approach to per-task logs by enforcing the Issue Entry Template and maintaining a persistent Issues Log to ensure blockers and workarounds are traceable alongside the task.

Related Skills

Explore More Content & Communication Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
alon21034alon21034
1

sprint-finish

Resolve non-terminal tasks and mark a sprint complete.

Community
Basic
Ethical-AI-SyndicateEthical-AI-Syndicate
1

blocker-resolution-advisor

Diagnose sprint blockers by type, severity, and root cause.

Official
Intermediate
GeneralJerelGeneralJerel
6

create-incident-report

Generate structured incident reports with timeline, impact, root cause, and action items.

Community
Advanced