skills.rest
akaszubski
akaszubskiCOMMUNITY
Explore all skills by this author →
GitHub

project-management

Generate PROJECT.md templates with goals, scope, and sprint planning.

32|5|Updated Oct 19, 2025
Search Tags:#project management#roadmap#sprint planning#goals#scope#okr#smart goals
One-click install
npx skills add https://github.com/akaszubski/autonomous-dev --skill project-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-management
Source: https://github.com/akaszubski/autonomous-dev/tree/main/plugins/autonomous-dev/skills/project-management
Command: npx skills add https://github.com/akaszubski/autonomous-dev --skill project-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear project goals, undefined scope, and chaotic sprint planning lead to missed deadlines and wasted effort. This skill provides structured templates and best practices for "PROJECT.md-first" development, ensuring clarity, alignment, and efficient execution.

Core Features & Use Cases

  • PROJECT.md Template: A comprehensive structure for defining project goals, scope, constraints, architecture, and roadmap in a single, living document.
  • Goal-Setting Frameworks: Guidance on using SMART goals and OKRs (Objectives & Key Results) to create measurable and impactful objectives.
  • Scope Definition: Best practices for "In vs. Out" and MoSCoW methods to clearly define project boundaries and prevent scope creep.
  • Use Case: When kicking off a new project, use this skill to create a robust PROJECT.md file, define clear SMART goals, and establish a detailed sprint plan, setting your team up for success.
  • Use Case: Validate new feature requests against existing project goals and scope, ensuring all work contributes to strategic objectives.

Quick Start

This is a knowledge skill, auto-activated by relevant keywords.

To get guidance on project management, simply ask:

"Help me define SMART goals for my new feature." "What should be included in a PROJECT.md file?"

Frequently Asked Questions about project-management

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

FAQPage Schema
How do I structure a PROJECT.md file for clear goal and scope documentation?▼

A PROJECT.md file organizes goals, scope, constraints, architecture, roadmap, risks, and sprints in one living document. This template-driven structure prevents unclear objectives and undefined scope by centralizing project decisions, enabling team alignment and reducing missed deadlines caused by scattered documentation.

What's the difference between SMART goals and OKRs for project planning?▼

SMART goals are Specific, Measurable, Achievable, Relevant, and Time-bound objectives for individual tasks. OKRs (Objectives & Key Results) set broader strategic outcomes with measurable key results. Both frameworks eliminate vague goals; choose SMART for tactical execution and OKRs for long-term strategic alignment.

How do I prevent scope creep and define project boundaries?▼

Use MoSCoW prioritization (Must, Should, Could, Won't) and "In vs. Out" scope definition to explicitly list what's included and excluded. This prevents scope creep by establishing clear boundaries upfront, ensuring all work contributes to strategic objectives rather than expanding indefinitely.

How do I plan sprints and align them with project roadmaps?▼

Sprint planning maps short-term work to long-term roadmap goals by breaking roadmap milestones into sprint-sized tasks with clear deliverables. Validate each sprint's work against project goals and scope to maintain strategic alignment and prevent off-track execution.

Can I validate feature requests against existing project goals and scope?▼

Yes. Compare new feature requests to your PROJECT.md goals, scope boundaries, and roadmap priorities using MoSCoW or OKR frameworks. This validation ensures incoming work aligns with strategic objectives and prevents scope creep from unvetted requests.

What should I include in a project roadmap section?▼

A project roadmap documents planned milestones, timelines, dependencies, and how each phase advances strategic goals. Include key deliverables, resource allocation, and cross-references to sprint plans and ADRs so teams understand both the "what" and the "why" behind execution sequencing.

Related Skills

Explore More Product & Management Skills→
qa-amanqa-aman
19

brd-writer

Draft comprehensive BRDs from user input with objectives, scope, constraints, and risks.

Community
Advanced
ryan-nguyen-01ryan-nguyen-01
4

agent-pm

Coordinate product delivery from backlog to release with structured templates.

Community
Advanced
avgarciaavgarcia

adr-review

Review architecture decision records for missing decisions, risks, and structural gaps.

Community
Advanced
vuminhieuvuminhieu

mermaidjs-v11

Render Mermaid.js v11 diagrams to SVG, PNG, or PDF via CLI.

Community
Intermediate