J-Pster/Psters_AI_Workflow

J-Pster/Psters_AI_Workflow

Command Claude Code

Use this command to implement changes in this plugin repository safely.

J-Pster/Psters_AI_Workflow

Command Claude Code

Use this command to publish a new plugin release.

J-Pster/Psters_AI_Workflow

Command

Read-only cross-artifact analysis for plans/docs/tasks consistency. Detects gaps, duplication, ambiguity, and unmapped work.

J-Pster/Psters_AI_Workflow

Command

Deploy Lambda functions using the guaranteed deploy scripts only. Never deploy via IAC (CDK). Requires AWS SSO login first. Use when deploying any AWS Lambda repo.

J-Pster/Psters_AI_Workflow

Command

Feature exploration and decision-making. Spawns 3 focused agents to research the feature, then resolves open questions through dialogue. Output is a concise decision document — the base for /pwf-plan. Saves to docs/brainstorms/.

J-Pster/Psters_AI_Workflow

Command

Generate requirement-quality checklists (not implementation tests) for a target plan or feature in docs/plans/ /checklists/.

J-Pster/Psters_AI_Workflow

Command

Ask up to 5 high-impact clarification questions for a plan/feature scope, then write a clarifications artifact in docs/plans/.

J-Pster/Psters_AI_Workflow

Command

Commit uncommitted changes across all workspace repos, tagging commits with ticket numbers from pasted issue text. Spawns one parallel subagent per repo — each analyzes every changed file, groups them by ticket, and makes multiple focused commits independently.

J-Pster/Psters_AI_Workflow

Command

Document a recently solved problem OR a new implementation pattern to accumulate team knowledge. Two modes: (1) /pwf-doc-capture [context] — document a bug/problem fix in docs/solutions/. (2) /pwf-doc-capture pattern [context] — document a reusable implementation pattern in docs/solutions/patterns/. Writes to…

J-Pster/Psters_AI_Workflow

Command

Create or refresh the project's foundation documentation set in docs/: infrastructure, architecture, integrations, environments, and glossary. Prevents drift by updating existing files instead of creating duplicates.

J-Pster/Psters_AI_Workflow

Command

Refresh and curate docs/solutions/ entries using an interactive lifecycle: Keep, Update, Replace, or Archive. User approval is required before any write action.

J-Pster/Psters_AI_Workflow

Command

Create or refresh operational runbooks under docs/runbooks/ with incident-ready structure (diagnosis, mitigation, rollback, escalation, and post-incident follow-up).

J-Pster/Psters_AI_Workflow

Command

Documentation command. Modes: (1) /pwf-doc lambda — Lambda doc, (2) /pwf-doc lambdas — all Lambdas, (3) /pwf-doc module — backend module doc, (4) /pwf-doc feature — frontend feature doc, (5) /pwf-doc architecture — system architecture overview, (6) /pwf-doc update — scan all docs for staleness and contradictions, (7)…

J-Pster/Psters_AI_Workflow

Command

Explain all available Psters Workflow commands and the recommended end-to-end flow. Read-only guidance command for onboarding and quick orientation.

J-Pster/Psters_AI_Workflow

Command

Create a detailed, execution-ready implementation plan. Thorough research + review agents ensure each phase can be executed directly by /pwf-work-plan without additional planning. Saves to docs/plans/.

J-Pster/Psters_AI_Workflow

Command

Multi-agent code review. Runs contextual review agents based on what was changed. No compound-engineering.local.md dependency.

J-Pster/Psters_AI_Workflow

Command

Create or repair the recommended multi-root project layout with separate Repos and Workspace folders, plus a .code-workspace file that Cursor/VS Code can open directly.

J-Pster/Psters_AI_Workflow

Command

Initialize or repair the project workflow skeleton under docs/. Creates required folders, starter README files, .gitkeep markers for empty directories, operational override policy file, required foundation docs, and runbooks structure.

J-Pster/Psters_AI_Workflow

Command

Lightweight execution path for trivial changes (small fix/cosmetic/local refactor) with minimal overhead and core safety checks.

J-Pster/Psters_AI_Workflow

Command

Execute a plan phase from docs/plans/. Reads existing docs first, executes tasks directly from the plan, builds, then updates documentation. No intermediate planning. No tests.

J-Pster/Psters_AI_Workflow

Command

Execute implementation using optional TDD flow (red-green-refactor). Use only when user explicitly requests tests-first behavior.

J-Pster/Psters_AI_Workflow

Command

Execute free-form work. Reads existing docs, researches context, derives concrete tasks, implements, builds, and updates documentation. For plan-driven work use /pwf-work-plan.