skills.rest
l3ocho
l3ochoCOMMUNITY
Explore all skills by this author →
GitHub

issue-conventions

Enforce standardized issue titles, bodies, and wiki references across projects.

Updated Jan 26, 2026
Search Tags:#planning#templates#governance#conventions#issue#wiki#sprint
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill issue-conventions-l3ocho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-conventions
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/issue-conventions
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill issue-conventions-l3ocho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes issue titles, bodies, and wiki references to improve traceability and collaboration across teams.

Core Features & Use Cases

  • Enforces a consistent Sprint title format in all issues.
  • Ensures each issue body includes a Description, Implementation Wiki link, and Acceptance Criteria.
  • Supports governance workflows for sprint planning, RFCs/ADRs, and documentation tasks.

Quick Start

Follow the template to create new issues using standardized conventions.

Frequently Asked Questions about issue-conventions

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

FAQPage Schema
How do I standardize sprint issue titles and bodies across multiple projects?▼

To standardize sprint issues, you need a mandatory title format and a fixed body structure containing a description, implementation wiki link, and acceptance criteria to ensure traceability and consistent collaboration across teams.

What is the required structure for an issue body during sprint planning?▼

The required issue body structure for sprint planning includes a clear description, an implementation wiki link for reference, and defined acceptance criteria to validate task completion and maintain documentation governance.

How do I enforce wiki reference inclusion in issue templates?▼

Enforcing wiki reference inclusion requires generating issue templates that mandate a specific wiki link field within the body structure, ensuring all implementation details remain traceable during sprint planning and documentation governance.

Can I use standardized issue conventions for RFC and ADR creation?▼

Yes, standardized issue conventions apply directly to RFC and ADR creation by enforcing consistent title formats and body structures, which improves traceability and aligns architectural decisions with sprint planning workflows.

What's the best way to validate issue titles against governance conventions?▼

Validating issue titles against governance conventions involves applying a mandatory title format check during sprint planning, ensuring every newly created issue aligns with the standardized template before execution begins.

Why do inconsistent issue formats cause problems in sprint planning?▼

Inconsistent issue formats cause sprint planning problems by breaking traceability between tasks and documentation, making it difficult for teams to locate implementation wiki links and verify acceptance criteria.

Related Skills

Explore More Product & Management Skills→
semicolon-devteamsemicolon-devteam

create-sprint

Create a GitHub Project Sprint Issue with iteration details and goals.

Official
Intermediate
devCharuzudevCharuzu

agile-product-owner

Organize Agile backlog management and sprint execution with user stories and capacity planning.

Community
Advanced
nahisahonahisaho
69

system-architect

Generate Mermaid C4 diagrams and ADRs for system architecture design.

Community
Advanced
tabooestabooes
1

user-story

Convert user needs into user stories with Gherkin acceptance criteria.

Community
Intermediate