project-management

Propose, plan, and execute multi-file project changes with governance artifacts.

2|1|Updated Jan 20, 2026

Search Tags:#workflow #planning #communication #execution #task-management #proposal #artifact-management

Ready to run

npx skills add https://github.com/sraloff/gravityboots --skill project-management-sraloff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-management
Source: https://github.com/sraloff/gravityboots/tree/main/.agent/skills/project-management
Command: npx skills add https://github.com/sraloff/gravityboots --skill project-management-sraloff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through proposing, planning, and executing large, multi-file changes, ensuring alignment and reducing scope creep.

Core Features & Use Cases

Proposal & alignment: Before coding, generate a concise proposal capturing the approach and rationale.
Plan & execute: Break the approved proposal into granular tasks, milestones, and owners, tracked in memory and docs.
Artifact governance: Maintain ongoing traceability of decisions, blockers, and progress across planning and execution.

Quick Start

Draft a concise proposal and a granular plan outlining milestones, owners, and checkpoints.

Frequently Asked Questions about project-management

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

FAQPage Schema

How do I plan and execute complex multi-file changes without scope creep?▼

To manage complex multi-file changes, use a three-stage workflow: generate a concise proposal for alignment, break the approved plan into granular tasks with milestones and owners, and maintain artifact governance to track decisions, blockers, and progress, thereby preventing scope creep.

What is the best way to track blockers and decisions during an engineering sprint?▼

The best way to track blockers during an engineering sprint is through artifact governance, which maintains ongoing traceability of decisions, blockers, and progress across both planning and execution phases, ensuring all team members have synchronized visibility into project status.

Can I use a single workflow for proposing, planning, and executing large feature launches?▼

Yes, a single workflow can support large feature launches by satisfying the three-stage process: Proposal, Plan, and Execute. It applies governance artifacts and memory synchronization to ensure product development alignment from initial concept through final execution.

Do I need to define task ownership and milestones before starting multi-file project execution?▼

Yes, you need to define task ownership and milestones before execution. Breaking an approved proposal into granular tasks with assigned owners and checkpoints ensures multi-file project changes are tracked properly in memory and docs, maintaining alignment and reducing scope creep.

Why does product development require a proposal stage before planning and execution?▼

Product development requires a proposal stage to capture the approach and rationale before coding begins. This ensures team alignment on the proposed direction, which reduces scope creep and provides a solid foundation for breaking the work into actionable plans and execution tasks.