project-management

Structure issues and PRs with tool-agnostic naming and lifecycle conventions.

Updated May 9, 2020
One-click install
npx skills add https://github.com/Fenntasy/dotfiles --skill project-management-fenntasy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-management
Source: https://github.com/Fenntasy/dotfiles/tree/main/claude/skills/project-management
Command: npx skills add https://github.com/Fenntasy/dotfiles --skill project-management-fenntasy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent issues and PRs across teams slow reviews and create gaps in traceability. This convention provides a unified, tool-agnostic framework for how to structure issues and PRs, how to name them, and how to manage their lifecycle.

Core Features & Use Cases

  • Issue conventions: standard title format, structured descriptions, and clear scope discipline.
  • PR conventions: consistent titles, concise summary bullets, explicit test plans, and explicit references to related issues.
  • Naming consistency and lifecycle guidance to streamline reviews and maintain traceability across platforms and teams.
  • Use Cases: apply to GitHub Issues, Linear issues, and any PR-hosting platform to achieve predictable workflows, easier reviews, and better collaboration.

Quick Start

Review your current issues and PRs and begin applying the conventions to draft consistent titles, descriptions, and lifecycle notes.

Frequently Asked Questions about project-management

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

FAQPage Schema
How do I standardize issue titles and PR descriptions across different platforms?

To standardize issues and PRs, apply a tool-agnostic convention framework that governs title formats, structured descriptions, naming consistency, and explicit references across teams and platforms.

What is the best way to manage issue and PR lifecycle for consistent traceability?

Managing issue and PR lifecycle for traceability requires applying unified scope discipline, mandatory sections, and lifecycle rules to ensure consistent communication throughout software projects.

Can I use these project management conventions with GitHub Issues and Linear?

Yes, these conventions are tool-agnostic and apply directly to GitHub Issues, Linear, and any PR-hosting platform to achieve predictable workflows and easier reviews.

How do I structure pull requests to streamline code reviews?

To streamline reviews, structure pull requests with consistent titles, concise summary bullets, explicit test plans, and explicit references to related issues for better collaboration.

Why do inconsistent issues and PRs slow down development teams?

Inconsistent issues and PRs slow reviews and create gaps in traceability because they lack a unified framework for structure, naming, and lifecycle management across cross-functional teams.

Do I need any specific tools or dependencies to start applying issue and PR conventions?

No specific tools or dependencies are required. Simply review your current issues and PRs and begin applying the conventions to draft consistent titles, descriptions, and lifecycle notes.