Run any Skill in Manus with one click

pm-spec-author

Stars1

Forks1

UpdatedJune 4, 2026 at 20:32

Interview a product manager and draft a code-grounded, dev-ready MWPW spec — reading real code (Scout), content (Odin), and architecture (CLAUDE.md) so the spec references actual files, variants, fragments, and locales. Use when a PM wants to write a spec, propose a feature, or turn an idea into a ticket. Activates on "write a spec", "spec this out", "I want a feature", "draft a ticket for", "turn this into a spec".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

adobecom

adobecom/mas-claude-config

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	pm-spec-author
description	Interview a product manager and draft a code-grounded, dev-ready MWPW spec — reading real code (Scout), content (Odin), and architecture (CLAUDE.md) so the spec references actual files, variants, fragments, and locales. Use when a PM wants to write a spec, propose a feature, or turn an idea into a ticket. Activates on "write a spec", "spec this out", "I want a feature", "draft a ticket for", "turn this into a spec".
tags	["pm","spec","authoring","mwpw","scout","odin"]

PM Spec Author

Purpose

Turn a PM's feature idea into a developer-ready MWPW spec grounded in the real codebase and content — not guesses. The PM brings product judgment; this skill brings codebase/content truth.

Preconditions

Run pm-prior-art first. If a duplicate exists, stop and recommend extending it.

Steps

Interview the PM (one question at a time): problem, target users, acceptance criteria, scope boundaries, target locales.
Ground in real code using Scout (local checkout):
- mcp__scout__search / mcp__scout__explain_symbol to find the real components/variants involved (e.g. confirm which merch-card variants exist before claiming a new one is needed).
- Read the relevant CLAUDE.md architecture docs for the affected layer.
Ground in real content using Odin where the spec touches fragments:
- mcp__odin-prod__search-aem-content-fragments to confirm which fragments/variants/locales exist — surface content gaps (e.g. "de_DE fragment missing") as dependencies.
Draft the spec in this structure:
- Problem — one paragraph, user-facing.
- Target users — who and in what context.
- Proposed change — what changes, referencing REAL files/variants/fragments.
- Acceptance criteria — testable, PM-authored.
- Affected areas — actual file paths (from Scout) and fragments (from Odin).
- Open questions / dependencies — incl. any content gaps found.
Hand off to filing: offer to file via the jira-ticket-creator skill (which handles MWPW required fields). Pass the drafted spec as the description.

Discipline

Never claim a file/variant/fragment exists without confirming it via Scout/Odin.
If Scout returns nothing for a claimed component, say so — don't fabricate paths.
Keep the spec scannable: one fact per bullet, no preambles.

More from this repository

same repository

adversarial-swarm

adobecom/mas-claude-config

Spawn 6 parallel adversarial sub-agents to audit a worktree or diff range from distinct personas (security, auth, ReDoS, dead-code, API contract, performance), then dedupe and rank findings via coordinator. Use for compressed multi-day audits. Activates on "adversarial swarm", "parallel audit", "swarm audit".

2026-07-081

audit-wave

adobecom/mas-claude-config

Scaffold a 4-wave architectural audit (smoke → security → hardening → deliverables) for a branch with characterization-test discipline. Use for pre-review audits of large MWPW branches (1000+ LOC, multiple features). Activates on "audit this branch", "wave audit", "pre-review audit", "architectural review".

2026-07-081

card-variant-registry

adobecom/mas-claude-config

Reference for all merch-card variants, their field schemas, CSS classes, and slot mappings. Use when adding new variants, debugging variant rendering, or understanding variant differences. Activates on "card variant", "variant fields", "variant schema", "add variant", "variant slots", "variant rendering".

2026-07-081

jira-ticket-creator

adobecom/mas-claude-config

Create, file, open, make, or log Jira tickets in the MWPW project via corp-jira MCP. Handles required fields (team, component, issue type) automatically. Use when the user wants to create/file/open/make/log a Jira ticket, task, story, bug, or issue — any phrasing including "create jira", "file a ticket", "open a story", "make a bug", "log a ticket", "new MWPW ticket", "raise a bug".

2026-07-081

mas-pr-creator

adobecom/mas-claude-config

Automatically detect PR creation intent and guide the process. Extracts JIRA ticket from branch, generates proper PR title and body, runs pre-flight checks, and creates PR using gh CLI. Use when user wants to create/raise/submit a PR.

2026-07-081

mas-pr-review

adobecom/mas-claude-config

Deep MAS-aware PR review for Milo or MAS pull requests using parallel domain agents (security, correctness, MAS contracts, coverage). Default to multi-agent fan-out; degrade to single-pass for narrow PRs. Verifies findings against current source before posting. Activates on "/mas-pr-review", "review PR", "review this PR", "second pass review", "another round of review", "audit PR", "deep PR review".

2026-07-081

name	pm-spec-author
description	Interview a product manager and draft a code-grounded, dev-ready MWPW spec — reading real code (Scout), content (Odin), and architecture (CLAUDE.md) so the spec references actual files, variants, fragments, and locales. Use when a PM wants to write a spec, propose a feature, or turn an idea into a ticket. Activates on "write a spec", "spec this out", "I want a feature", "draft a ticket for", "turn this into a spec".
tags	["pm","spec","authoring","mwpw","scout","odin"]

PM Spec Author

Purpose

Turn a PM's feature idea into a developer-ready MWPW spec grounded in the real codebase and content — not guesses. The PM brings product judgment; this skill brings codebase/content truth.

Preconditions

Run pm-prior-art first. If a duplicate exists, stop and recommend extending it.

Steps

Interview the PM (one question at a time): problem, target users, acceptance criteria, scope boundaries, target locales.
Ground in real code using Scout (local checkout):
- mcp__scout__search / mcp__scout__explain_symbol to find the real components/variants involved (e.g. confirm which merch-card variants exist before claiming a new one is needed).
- Read the relevant CLAUDE.md architecture docs for the affected layer.
Ground in real content using Odin where the spec touches fragments:
- mcp__odin-prod__search-aem-content-fragments to confirm which fragments/variants/locales exist — surface content gaps (e.g. "de_DE fragment missing") as dependencies.
Draft the spec in this structure:
- Problem — one paragraph, user-facing.
- Target users — who and in what context.
- Proposed change — what changes, referencing REAL files/variants/fragments.
- Acceptance criteria — testable, PM-authored.
- Affected areas — actual file paths (from Scout) and fragments (from Odin).
- Open questions / dependencies — incl. any content gaps found.
Hand off to filing: offer to file via the jira-ticket-creator skill (which handles MWPW required fields). Pass the drafted spec as the description.

Discipline

Never claim a file/variant/fragment exists without confirming it via Scout/Odin.
If Scout returns nothing for a claimed component, say so — don't fabricate paths.
Keep the spec scannable: one fact per bullet, no preambles.