project-mgmt

Create and maintain a project.md documenting requirements, design decisions, and constraints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RushuiGuan/claude --skill project-mgmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-mgmt
Source: https://github.com/RushuiGuan/claude/tree/main/skills/project-mgmt
Command: npx skills add https://github.com/RushuiGuan/claude --skill project-mgmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The project-mgmt skill provides a centralized blueprint for documenting a project's purpose, business requirements, technical design decisions, key architectural choices, open questions, and constraints, all in a single project.md at the project root.

Core Features & Use Cases

  • Create and maintain a single project.md under project-mgmt/ to capture why the project exists, what needs to be solved, and how decisions were reached.
  • Consolidate Business Requirements, Technical Design, Open Questions, and Dependencies into one authoritative source that spans all tasks and artifacts.
  • Use this document to review decisions, rationale, and status across the project, ensuring a consistent context for new work or design discussions.

Quick Start

Create or update project-mgmt/project.md to record the project's purpose, requirements, decisions, and design context.

Frequently Asked Questions about project-mgmt

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

FAQPage Schema
How do I maintain project documentation for business requirements and technical design in one place?

Project documentation for business requirements and technical design is maintained in a single project.md file. This file serves as a centralized blueprint to capture project purpose, decisions, and constraints across all tasks.

What is the best way to document architectural decisions and rationale for a software project?

Documenting architectural decisions and rationale is handled by recording key design choices and constraints in a structured project.md file. This ensures a consistent context for new work and design discussions by serving as an authoritative source.

How do I track open questions and dependencies during project management?

Tracking open questions and dependencies during project management involves organizing them into dedicated sections within a single project documentation file. This approach consolidates project status and constraints into one authoritative source.

Does this project documentation approach work without external dependencies?

This project documentation approach works without external dependencies because it relies solely on creating and maintaining a single markdown file. You only need a text editor to capture business requirements and technical design context.

When do I need a single source of truth file for project context?

A single source of truth file for project context is needed when you must consolidate business requirements, technical design, and open questions across multiple tasks. It ensures all team members review consistent decisions and rationale.