agentleFS
Sign inStart free
timjrobinsontimjrobinson/Claude-Code-Construction-Manager/.claude/skills/phase-plan/SKILL.md

phase-plan

Skill4 starsChanged 8 months agoMITView on GitHub

Creates or updates a construction phase plan based on current milestone, completed work, and available capacity.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is invoked:

    line 11
  2. Very specific:

    Read current milestone from production/milestones/.

    line 13
  3. Very specific:

    Read previous phase plan (if any) from production/phases/.

    line 14
  4. Distinctive:

    Check risk register if it exists.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When this skill is invoked:

  1. Read current milestone from production/milestones/.
  2. Read previous phase plan (if any) from production/phases/.
  3. Scan design documents in design/ for deliverables status.
  4. Check risk register if it exists.

For new:

Generate a phase plan:

# Phase [N] — [Start Date] to [End Date]

## Phase Goal
[One sentence describing what this phase achieves]

## Capacity
- Total weeks: [X]
- Buffer (15%): [Y weeks reserved]
- Available: [Z weeks]

## Tasks

### Critical Path
| ID | Task | Discipline | Duration | Dependencies | Acceptance Criteria |
|----|------|-----------|----------|-------------|-------------------|

### Important
| ID | Task | Discipline | Duration | Dependencies | Acceptance Criteria |
|----|------|-----------|----------|-------------|-------------------|

### If Time Allows
| ID | Task | Discipline | Duration | Dependencies | Acceptance Criteria |
|----|------|-----------|----------|-------------|-------------------|

## Risks
| Risk | Probability | Impact | Mitigation |
|------|------------|--------|------------|

## Budget
| Category | Budgeted | Committed | Spent | Variance |
|----------|---------|-----------|-------|----------|

For status:

Generate status report with progress, blockers, and burndown assessment.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free