repo-pm-feature-workflow

# PM Feature Workflow Use this skill when the user asks for high-level execution, such as "what is next", "plan and implement", or "take the next issue". ## Goal Run a deterministic feature workflow so the user can act as product manager while the agent handles planning and delivery steps. ## Workflow 1. Select the next candidate from GitHub Issues and [Project #8](https://github.com/users/markheydon/projects/8). 2. Confirm scope alignment in `plan/SCOPE.md`. 3. Trigger planning with `breakdown-plan`. 4. For any feature that will result in a new page, a new major page region, or a substantive page refresh, create a wireframe in `plan/wireframes/` and update `plan/wireframes/README.md` before implementation begins. 5. Create or update GitHub issues with `repo-github-issues` (use `repo-github-gh-cli` for bulk changes), then sync each issue to the project board with `repo-github-project` skill. 6. Trigger quality planning with `breakdown-test`. 7. Run implementation preflight (load context, codebase discovery, sketch). For `size/l+` or enablers, consider standalone `preflight-issue` first. 8. Implement using repository standards (`aspire` plus `dotnet-best-practices`, and `mudblazor` for UI work), with MudBlazor components and utility classes preferred over custom CSS or raw HTML. Rebuild the live Aspire `app` resource after C# or Razor fixes; inspect Aspire logs on exceptions. 9. Record architectural decisions via `repo-decision-log` when introduced. 10. Update user-facing documentation and index links. 11. Verify completion gates and then close issue states. ## Mandatory Gates - Do not code before planning artefacts and issue records are complete. - Do not start coding before implementation preflight completes (context loaded, touch map produced, proceed gate satisfied). - Do not start page-producing UI implementation until the planning wireframe exists and is referenced by the relevant issue or artefact. - Do not close work before tests and documentation updates are complete. - Any scope change must update `plan/SCOPE.md` and `plan/IMPLEMENTATION_PLAN.md`, and create or update the corresponding GitHub Issue. - Any architectural decision must follow `repo-decision-log` (constitution and/or `plan/DECISIONS.md`). ## Required Artefacts Per Feature - GitHub Issue create/update + Project #8 sync (including `## Implementation References` in issue bodies) - Scope update when needed: `plan/SCOPE.md` - Wireframe: `plan/wireframes/*.md` and `plan/wireframes/README.md` for any page-producing feature or substantive page refresh - Decision log when needed: `plan/DECISIONS.md` - User guide stub when user-facing: `website/content/docs/*.md` - Docs index quick links when a new page is added: `website/content/_index.md` ## Prompt Starters - "What is the next issue? Plan it and execute the implementation workflow." - "Take the next backlog story and run full PM feature workflow." - "Plan, create issues, implement, test, and document this feature end-to-end."