save-docs

Save product vision, user stories, and backlog as Markdown files in the docs/ directory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/686f6c61/PSPO-Agent --skill save-docs-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-docs
Source: https://github.com/686f6c61/PSPO-Agent/tree/main/skills/save-docs
Command: npx skills add https://github.com/686f6c61/PSPO-Agent --skill save-docs-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all product artifacts generated by the plugin are persistently saved in Markdown format to the local file system, acting as a safety net even if remote systems are unavailable.

Core Features & Use Cases

  • Local Persistence: Saves product vision, user stories, and backlog to the docs/ directory.
  • Structured Documentation: Creates individual Markdown files for each user story with detailed fields and criteria.
  • Use Case: After defining your product vision and user stories, use this Skill to save everything locally, ensuring your work is backed up and easily accessible in a human-readable format.

Quick Start

Use the save-docs skill to persist all current product artifacts to the local file system.

Frequently Asked Questions about save-docs

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

FAQPage Schema
How do I save user stories and product backlog locally in Markdown?

To save user stories and backlog locally in Markdown, you can persist product artifacts into individual structured files within the `docs/` directory. It uses predefined templates to store detailed fields and criteria for each story.

What is the best way to back up product artifacts without relying on remote services?

Saving product artifacts to local Markdown files provides a reliable backup without relying on remote services. It acts as a safety net, maintaining a consolidated backlog file and ensuring your work remains accessible in a human-readable format.

How does local Markdown persistence work for product vision and backlog?

Local Markdown persistence works by writing product vision and backlog items directly to your local file system. It creates individual Markdown files for each user story and maintains a consolidated backlog file in the `docs/` directory.

Do I need a remote project management tool to store my backlog and user stories?

You do not need a remote project management tool to store your backlog and user stories. This local persistence approach ensures data independence by saving predefined structured templates directly into the `docs/` directory.

Can I save individual user stories with detailed acceptance criteria in Markdown?

Yes, you can save individual user stories with detailed acceptance criteria in Markdown. The process creates individual files for each story using predefined templates to ensure structured documentation of all fields and criteria.