agentsclimarketplace

Project planning

Skill devsforge/orchestrator/skills/project-planning

Expert knowledge in project planning, requirements gathering, user stories, and scope management. Use when planning new projects or features.From its SKILL.md

Install
npx -y skills add devsforge/orchestrator --skill project-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.9 KB, as published. Nobody here has run it

Project Planning Skill

Comprehensive knowledge for planning software projects from ideation to execution.

Planning Methodology

1. Discovery Phase

Questions to Ask:

  • What problem are we solving?
  • Who are the target users?
  • What does success look like?
  • What are the constraints?
  • What's the timeline?

2. Requirements Gathering

Requirement Types:

  • Functional: What the system must do
  • Non-Functional: How well it must do it
  • Technical: Implementation constraints
  • Business: Organizational needs

3. User Story Format

**As a** [type of user]
**I want** [goal/desire]
**So that** [benefit/value]

**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

**Priority:** P0/P1/P2
**Estimate:** S/M/L/XL

4. Prioritization Framework

MoSCoW Method:

  • Must Have: Critical for MVP
  • Should Have: Important but not critical
  • Could Have: Nice to have
  • Won't Have: Out of scope (for now)

Priority Levels:

PriorityDescriptionTimeline
P0CriticalImmediate
P1HighThis sprint
P2MediumNext sprint
P3LowBacklog

5. Estimation Techniques

T-Shirt Sizing:

SizeComplexityTime
XSTrivial< 1 hour
SSimple1-4 hours
MMedium4-8 hours
LComplex1-3 days
XLVery Complex> 3 days

Story Points (Fibonacci): 1, 2, 3, 5, 8, 13, 21

6. Scope Management

In Scope:

  • Explicitly defined features
  • Agreed requirements
  • Documented acceptance criteria

Out of Scope:

  • Features deferred to future
  • Explicitly excluded items
  • Nice-to-haves beyond MVP

7. Risk Assessment

RiskLikelihoodImpactMitigation
Scope creepHighHighStrict change control
Technical debtMediumMediumRegular refactoring
Key person dependencyMediumHighDocumentation, pairing

Templates

Project Brief Template

# Project: [Name]

## Overview
[1-2 sentence description]

## Problem Statement
[What problem does this solve?]

## Goals
1. [Primary goal]
2. [Secondary goal]
3. [Tertiary goal]

## Success Metrics
- [Metric 1]: [Target]
- [Metric 2]: [Target]

## Scope
### In Scope
- [Feature 1]
- [Feature 2]

### Out of Scope
- [Excluded 1]
- [Excluded 2]

## Timeline
- Phase 1: [Date]
- Phase 2: [Date]
- Launch: [Date]

Epic Template

# Epic: [Name]

## Description
[What this epic accomplishes]

## User Stories
- [ ] US-001: [Story]
- [ ] US-002: [Story]

## Acceptance Criteria
- [ ] [Criterion]

## Dependencies
- [Dependency 1]

Keep looking

Skills are one crate of 614,327. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.