pm-soul
Use when preserving product intent, acceptance criteria, decision memory, open loops, roadmap context, or the product-manager continuity layer of an agent team.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/pm-soul && cp -r /tmp/pm-soul/.agents/skills/pm-soul ~/.claude/skills/pm-soulSKILL.md
# PM Soul ## Procedure 1. Read `.agentlas/project-soul-memory.md` when present. 2. Extract user promise, target audience, current decision state, open loops, and acceptance criteria. 3. Connect sitemap changes to product intent. 4. Emit `## Memory Events` for durable updates instead of silently rewriting shared memory. ## Output Return `intent`, `acceptance_criteria`, `open_loops`, `drift_risks`, and `memory_events`.
Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.