skills.rest
metasaver
metasaverCOMMUNITY
Explore all skills by this author →
GitHub

save-prd

Persist approved PRD artifacts into a dated project directory.

Updated Aug 27, 2026
Search Tags:#automation#workflow#documentation#prd#hitl
One-click install
npx skills add https://github.com/metasaver/claude-marketplace --skill save-prd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save-prd
Source: https://github.com/metasaver/claude-marketplace/tree/main/plugins/metasaver-core/skills/workflow-steps/save-prd
Command: npx skills add https://github.com/metasaver/claude-marketplace --skill save-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill saves approved PRD artifacts into a structured project directory, enabling reliable build-time access to PRDs and related artifacts.

Core Features & Use Cases

  • Automated artifact persistence: prd.md, user stories, execution plan, and architecture notes saved to docs/projects.
  • Lifecycle integration: Works after HITL approval to finalize documentation for /build execution.
  • Structured output: Consistent directory layout for downstream workflows.

Quick Start

After HITL approval, run the save-prd step to persist artifacts under docs/projects/{yyyymmdd}-{name}/.

Frequently Asked Questions about save-prd

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

FAQPage Schema
How do I automate saving PRD documentation to my project after approval?▼

Save-prd persists approved PRD artifacts automatically to a structured docs/projects directory after HITL approval, creating dated folders with prd.md, user stories, execution plan, and architecture notes ready for build execution.

What files and structure does a PRD artifact save create?▼

The workflow generates docs/projects/{yyyymmdd}-{name}/ containing prd.md with goals and requirements, individual US-{NNN}-{slug}.md user story files, execution-plan.md with wave schedules and agent assignments, optional innovations-selected.md, and architecture-notes.md.

When should I use automated PRD persistence in my documentation workflow?▼

Use this after HITL approval to finalize and persist PRD artifacts, ensuring consistent structured output for downstream /build execution and enabling reliable access to approved documentation without manual file handling.

Can I include innovation documentation alongside my PRD output?▼

Yes, the skill optionally writes innovations-selected.md as part of artifact persistence, allowing you to document selected innovations alongside your core PRD, user stories, and execution plan in the same project folder.

What happens after PRD artifacts are saved to the project directory?▼

The skill outputs the absolute path to your saved prd.md and instructs you to run /build with that path, enabling the next stage of your workflow to access the finalized, structured documentation.

Related Skills

Explore More Software Engineering Skills→
stephschofieldstephschofield

prd

Generate a structured Product Requirements Document from a feature idea.

Community
Advanced
bartoszwarzochabartoszwarzocha

session-protocol

Save and load JSON session state with /save-session and /load-session commands.

Community
Advanced
m-ahmad-officialm-ahmad-official

approval_workflow

Scan pending approval directories and list items awaiting human authorization.

Community
Advanced
expectedparrotexpectedparrot

edsl-persistence-reference

Save and load EDSL Surveys, Agents, and AgentLists locally and in the cloud.

Official
Intermediate