agentleFS
lalulalilalulali/vespyr/.agents/skills/phase/SKILL.md

phase

Skill11 starsChanged 10 days agoMITView on GitHub

Show current phase, switch phases, list phase artifacts. Use when the user says "what phase are we in", "switch to the design phase", "what has been produced so far", or invokes /phase.

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

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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. Very specific:

    Read artifacts/output/pipeline-state.json (or execute node .agents/scripts/orchestrator_state.js status) to read the canonical …

    line 43
  2. Very specific:

    If not initialized, fall back to reading artifacts/memory/project-context.md for the current phase, or infer from the latest artifact in …

    line 45
  3. Distinctive:

    If the user requests a phase switch:

    line 79

“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

Phase — Pipeline Phase Control

What this skill does

Displays the current phase in the product pipeline, allows switching between phases, and lists the artifacts produced in each phase.

When to use

  • "What phase are we in?"
  • "Switch to design phase"
  • "Show me what's been produced so far"
  • "What phase should I be in for X?"

Pipeline phases

PhaseSkillKey Output
-1: Validationvalidate-ideaValidation brief (GO/RESHAPE/NO-GO)
0: Discoveryexplore-ideaIdea brief
1: Researchexplore-ideaMarket analysis, personas, competitive landscape
2: StrategydesignPRD, user stories, product spec
3: ArchitecturedesignADRs
4: PlanningplanExecution plan, task estimates, Kanban
5: ExecutiondevelopWorking, tested feature
6: LaunchlaunchShipped feature in production
7: IterationiterateMeasured improvement
8: Documentation(cross-cutting)Current docs
9: RetrospectiveretroAction items for improvement
Any: IncidentincidentMitigated incident, RCA

Workflow

Step 1: Detect current phase

Read artifacts/output/pipeline-state.json (or execute node .agents/scripts/orchestrator_state.js status) to read the canonical "current_phase".

If not initialized, fall back to reading artifacts/memory/project-context.md for the current phase, or infer from the latest artifact in artifacts/output/:

  • 01-discovery/ has content → discovery
  • 02-research/ has content → research
  • 03-strategy/ has content → strategy
  • 04-architecture/ has content → architecture
  • 05-planning/ has content → planning
  • 05-execution/ has content → execution
  • 06-launch/ has content → launch
  • 07-iteration/ has content → iteration
  • 08-documentation/ has content → documentation
  • 09-retro/ has content → retro

Step 2: Report

Answer the question asked, and do not re-render the snapshot.

If the user asked "what phase are we in?" — say the phase, its status, and the next action:

## Current Phase: {phase name}
**Status:** {status from pipeline-state.json's phases[phase]}
**Next:** {Run `node .agents/scripts/orchestrator_state.js next`}

If the user asked "what's been produced?" — list the current phase's artifacts and versions.

For anything wider — blockers, change requests, the last session, memory health, artifacts across all phases — point at /status rather than restating it. This skill used to render a full report whose every field /status already produces, in a different shape, from the same file. Two renderings of one source drift, and a reader cannot tell which is current. /status is the snapshot; this skill owns exactly one thing it does not: switching the phase (Step 3).

Step 3: Switch phase (on request)

If the user requests a phase switch:

  1. Run:
    node .agents/scripts/orchestrator_state.js set-phase --phase {targetPhase}
    (Note: This programmatically updates the current_phase, records it in the history, sets appropriate in-progress timestamps, and automatically syncs artifacts/memory/project-context.md's Phase: field).
  2. Log the change to artifacts/memory/active-decisions.md
  3. Load the corresponding skill for the new phase

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.