Classifies work type and produces a structured product brief with acceptance criteria.
npx skills add https://github.com/anderson-joyle/claude-a-team --skill pm-anderson-joyle
Please help me install this Agent Skill. Skill: PM Source: https://github.com/anderson-joyle/claude-a-team/tree/main/skills/pm Command: npx skills add https://github.com/anderson-joyle/claude-a-team --skill pm-anderson-joyle
It converts an ambiguous software request into a structured product brief that makes scope, constraints, and measurable acceptance criteria explicit, reducing misalignment across downstream roles.
Use the PM skill when you need to produce a structured product brief with acceptance criteria from a normalized intake request and supporting evidence.
High-intent search queries and answers about installing and using this skill.
Acceptance criteria for software requirements should be structured as stable, ID-based objects suitable for verification. This approach ensures that work type classification and problem framing are explicit, and surfaces blocking questions when supporting evidence conflicts with the request description.
To define scope and constraints, classify the work type and articulate a precise problem statement comparing current versus expected behavior. This produces a structured product brief making scope, constraints, and measurable acceptance criteria explicit to reduce downstream misalignment.
Ground decisions in provided artifacts and evidence during the intake process to identify inconsistencies. When evidence conflicts with the user description, the system raises these discrepancies as explicit blocking questions before finalizing scope and acceptance criteria.
Yes, producing a structured product brief requires a normalized intake request and supporting evidence. The process classifies work type and defines scope by grounding decisions in these provided artifacts, ensuring inconsistencies are surfaced as blocking questions before proceeding.
Set the artifact_type to pm_output and assign the body to PMOutputBody within the shared artifact envelope. You must preserve the request_id, schema_version, and relevant parent_artifact_ids to maintain proper artifact tracking and schema integrity throughout the workflow.
anderson-joyleNormalize raw work requests into structured intake_output JSON artifacts.
AmiraultExecutes validated software specifications with automated build and test cycles.
JetXu-LLMTrace knowledge objects to evidence units and provenance records.
darkroomengineeringGuide structured interviews to define project scope and requirements.
