How do I install the Phased Prd Red Green skill?

Run npx skillmds@latest add tomevault-io/phased-prd-red-green in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Phased Prd Red Green safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Phased Prd Red Green?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Phased Prd Red Green free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Phased Prd Red Green?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Phased Prd Red Green by tomevault-io

Name: Phased Prd Red Green
Author: tomevault-io

Phased Prd Red Green

Create or update a phased PRD and then execute delivery using a strict red/green workflow. Use when a task spans multiple steps, has cross-cutting impact, needs explicit exit criteria, or requires reliable test-driven implementation sequencing. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Phased PRD + Red/Green Delivery

Overview

Use this skill to drive a task from planning to completion with explicit phase gates.

Read references/prd_red_green_template.md before writing a new PRD.

Workflow

Confirm scope, success target, and constraints.
Decide whether to create/update a PRD.
Draft or revise the PRD with phased red/green structure.
Execute each phase in order: red -> green -> refactor.
Track completion in the checklist and update status.

PRD Authoring Rules

Place documents in prd/.
Use dated file names: YYYY_MM_DD_<topic>_prd.md.
Include at minimum:
- Status
- Context
- Goals and non-goals
- Phased plan
- Exit criteria per phase
- Acceptance criteria
- Risks and mitigations
- Implementation checklist
Keep phases independently testable and incremental.

Red/Green Execution Rules

Write failing tests/checks first for each phase.
Record the failing signal (error, unsupported op, mismatch, or failing assertion).
Implement the smallest possible change set to pass.
Re-run targeted tests, then adjacent regression tests.
Refactor only after green and keep semantics unchanged.

Evidence And Reporting

Report which commands ran and which did not run.
Include key pass/fail outputs for each phase gate.
Do not mark a phase complete until exit criteria are verified.
Mark PRD as Completed only when all checklist items are done.

Reference

Use references/prd_red_green_template.md as the default skeleton and execution checklist.

Source: skryl/mlx-ruby — distributed by TomeVault.

---name: phased-prd-red-greendescription: Create or update a phased PRD and then execute delivery using a strict red/green workflow. Use when a task spans multiple steps, has cross-cutting impact, needs explicit exit criteria, or requires reliable test-driven implementation sequencing. Use when this capability is needed.---# Phased PRD + Red/Green Delivery## OverviewUse this skill to drive a task from planning to completion with explicit phase gates.Read `references/prd_red_green_template.md` before writing a new PRD.## Workflow1. Confirm scope, success target, and constraints.2. Decide whether to create/update a PRD.3. Draft or revise the PRD with phased red/green structure.4. Execute each phase in order: red -> green -> refactor.5. Track completion in the checklist and update status.## PRD Authoring Rules1. Place documents in `prd/`.2. Use dated file names: `YYYY_MM_DD_<topic>_prd.md`.3. Include at minimum: - Status - Context - Goals and non-goals - Phased plan - Exit criteria per phase - Acceptance criteria - Risks and mitigations - Implementation checklist4. Keep phases independently testable and incremental.## Red/Green Execution Rules1. Write failing tests/checks first for each phase.2. Record the failing signal (error, unsupported op, mismatch, or failing assertion).3. Implement the smallest possible change set to pass.4. Re-run targeted tests, then adjacent regression tests.5. Refactor only after green and keep semantics unchanged.## Evidence And Reporting1. Report which commands ran and which did not run.2. Include key pass/fail outputs for each phase gate.3. Do not mark a phase complete until exit criteria are verified.4. Mark PRD as `Completed` only when all checklist items are done.## ReferenceUse `references/prd_red_green_template.md` as the default skeleton and execution checklist.---> Source: [skryl/mlx-ruby](https://github.com/skryl/mlx-ruby) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions