Stats
Actions
Tags
From pmp
Use when the user says 'organize specs', 'arc42', 'consolidate docs', 'clean up specs', 'reorganize architecture', 'merge spec files', or has spec files that grew disorganized and need restructuring
How this skill is triggered — by the user, by Claude, or both
Slash command
/pmp:arc42The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Announce at start:** "Using pmp:arc42 to reorganize specifications."
Announce at start: "Using pmp:arc42 to reorganize specifications."
Reorganize spec/architecture files into the arc42 standard structure. Reads the corpus, classifies content into arc42's 12 sections, identifies duplicates and contradictions, proposes a new directory structure, and executes the reorganization after user approval.
Standalone workflow — does not feed into plan generation or execution.
Always ask before transitioning. Use AskQuestion. Never auto-advance.
Use agent teams (Task tool) ONLY for parallel file reading when the corpus is large. All analysis runs in the main controller context — do not spawn agents for analysis phases. Track progress with TodoWrite throughout.
docs/.cache/arc42/manifest.json. Load cached summaries for unchanged files, only read changed/new files in full. This is mandatory, not optional.npx claudepluginhub paixaop/my-claude-skills --plugin pmpGenerates arc42 architecture documentation using the 12-section template including introduction, constraints, views, and decisions. For design, planning, and best practices.
Creates ADRs in MADR format, arc42 documentation, and plan-context.md for architecture proposals. Handles branch verification, GitHub issue/PR creation, artifact triage, and backlog updates.
Write and manage spec files with search, conflict detection, and reporting. Use when user asks to create a spec, update a spec, write a spec, or mentions 스펙 생성, 스펙 업데이트, 스펙 작성, 스펙 만들어줘. Proactively trigger whenever the user's request involves specification documents, even if they don't explicitly say "spec".