From pact
Generates YAML PACT lifecycle flow documents for features by analyzing source code, covering purpose, invariants, states like fresh_install and error_paths, gotchas. Saves to docs/feature_flows/ after verbal summary verification.
npx claudepluginhub jonathanmr22/pact --plugin pactThis skill uses the workspace's default tool permissions.
Create a PACT lifecycle flow document for the feature the user specifies. Save it to `docs/feature_flows/{feature_name}_flow.yaml`.
Writes or updates backend feature documentation per repo's DOCUMENTATION_GUIDELINES.md, including architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.
Plans single features, endpoints, or infrastructure via Socratic conversation to uncover requirements, edge cases, failure modes, and constraints; outputs markdown feature plan artifact before coding.
Generates detailed specs for single features including user stories, acceptance criteria, user flows, edge cases, API definitions, scope, dependencies, and effort estimates.
Share bugs, ideas, or general feedback.
Create a PACT lifecycle flow document for the feature the user specifies. Save it to docs/feature_flows/{feature_name}_flow.yaml.
Read the relevant source code first to understand the feature's actual behavior. Then generate a YAML flow document covering:
fresh_install — what exists, what's empty, what's defaultednormal_open — numbered order of operations + assumptionsbackground — what's active, held in memory, lostforce_close_reopen — what's lost, what's persisted, recovery pathbackground_resume — what re-initializes, what gets checkederror_paths — what happens when things go wrongAfter generating, present a verbal summary of the flow to the user for verification before finalizing.
Do NOT duplicate table names, file paths, or provider names from SYSTEM_MAP.yaml — use system_map_section to point there instead. This file owns BEHAVIOR (temporal). The map owns STRUCTURE (spatial).