skills.rest
YYG501
YYG501COMMUNITY
Explore all skills by this author →
GitHub

pmai-record

Records confirmed project knowledge into designated truth-source files with guarded commits.

4|Updated May 26, 2026
Search Tags:#product management#git commit#decision log#terminology#todo tracking#workflow guardrails#knowledge recording
One-click install
npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-record-yyg501
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pmai-record
Source: https://github.com/YYG501/PM-AI-Harness/tree/main/skills/record
Command: npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-record-yyg501

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confirmed product decisions, stable terminology, cross-module rules, and follow-up todos often get lost after a discussion ends. This Skill writes already-confirmed project knowledge back into the correct truth-source files (TODO.md, PRODUCT-RULES.md, PRODUCT-STATE.md, decision records) as a separate, minimal commit, so nothing agreed upon is dropped. ## Core Features & Use Cases - Guarded Entry: Runs a product-baseline gate and refuses to write when the proposal is missing/invalid, active work exists, or staged WIP conflicts are present. - Strict Write Boundaries: Only writes to explicitly allowed truth-source files; never touches module docs, proposals, mockups, or workflow state. - Evidence-Based Correction: Updates PRODUCT-STATE.md only against facts already committed on main, never from discussion or WIP. - Use Case: After a discussion, the PM says "this terminology is settled, don't lose it." The Skill verifies the baseline, patches the glossary entry, stages only that file, and commits it with a receipt. ## Quick Start Tell the assistant to record the confirmed terminology or todo into the project using the pmai-record skill.

Frequently Asked Questions about pmai-record

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

FAQPage Schema
How do I save confirmed product decisions so they are not lost?▼

Use the record entry point after a decision is explicitly confirmed. It writes the conclusion into the appropriate truth-source file such as TODO.md, PRODUCT-RULES.md, or a decision record, then commits it separately with a short receipt.

When should I use record instead of proposal or design?▼

Use record only for knowledge that is already confirmed and belongs to no active work. New product direction judgments go to proposal, and changes to module objects, states, or acceptance rules go to design.

Why does record refuse to write anything?▼

It stops when the product baseline is missing or invalid, active module work exists, the worktree is not main, target files are missing, or staged WIP is present. Each stop condition points to the correct recovery entry such as status or doctor.

Can record update PRODUCT-STATE with newly discussed features?▼

No. PRODUCT-STATE corrections require facts already committed on main. Capabilities from discussion, mockups, or uncommitted work cannot be written as current state; they land only through the build and finalize flow.

Does record commit changes automatically?▼

For todos, terminology, and evidence-based state corrections, the PM's record request is sufficient authorization. Changes to PRODUCT-RULES.md or new decision records require showing the diff and getting PM confirmation before committing.

Related Skills

Explore More Product & Management Skills→
mattfustermattfuster

learning-capture

Capture learnings as structured records with recurrence detection and approval.

Community
Intermediate
JYbillJYbill
1

summary

Consolidate requirements, plans, and implementation into a stable docs/spec artifact.

Community
Intermediate
btseytlinbtseytlin
47

git-worktrees

Create an isolated Git worktree workspace with baseline tests.

Community
Intermediate
georgernstgrafgeorgernstgraf

knowledge-persistence

Persist session insights into docs/ai knowledge files at checkpoints.

Community
Intermediate