setup-pm-loadout

Configure PM Loadout workspace settings, canonical sources, and write permissions with explicit confirmation.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill setup-pm-loadout-ithaloazevedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-pm-loadout
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/setup-pm-loadout
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill setup-pm-loadout-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a product management skill library in a new workspace often involves unclear defaults, accidental writes to external tools, and scattered configuration. This Skill walks through a one-time, confirmation-gated setup so canonical context sources, authorized integrations, and persistence policies are explicit before any work begins. ## Core Features & Use Cases - Workspace Inspection: Reviews AGENTS.md, knowledge folders, installed skills, available connectors, and any existing local configuration before proposing changes. - Guided Configuration: Resolves language, canonical context sources, allowed persistence targets, authorized integrations, and write policy in a fixed order, asking only questions that change a decision. - Confirmed Writes Only: Copies the template to config/pm-loadout.local.yaml and applies only approved values after explicit confirmation, never storing secrets, tokens, or PII. - Use Case: On first use of PM Loadout in a new repo, run the setup to declare that ClickUp is unavailable, keep artifacts in the conversation, and record conservative defaults for future sessions. ## Quick Start Run the setup-pm-loadout skill to inspect this workspace and propose a confirmed PM Loadout configuration.

Frequently Asked Questions about setup-pm-loadout

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

FAQPage Schema
How do I set up PM Loadout in a new workspace?▼

Run the setup-pm-loadout skill once per workspace. It inspects the repository, shows what is defined and missing, resolves configuration decisions in order, and writes config/pm-loadout.local.yaml only after your explicit confirmation.

Does the setup write configuration without my approval?▼

No. The skill follows a write-confirmed policy: it proposes conservative template values, asks only questions that change a decision, and copies the template to config/pm-loadout.local.yaml only after you confirm.

Can I store API tokens or secrets in the PM Loadout config file?▼

No. The skill explicitly forbids storing secrets, tokens, PII, or card content in the configuration file. Available connectors are not treated as authorization to write.

What happens if ClickUp or other integrations are unavailable?▼

Unavailable integrations stay disabled in the configuration, and the skill delivers artifacts directly in the conversation instead. It never assumes ClickUp, databases, or context packs exist.

What happens when I rerun the setup skill?▼

Rerunning updates the existing configuration rather than replacing it. Fields unrelated to the current changes are preserved, so previous decisions remain intact.