Workflow Router

Run work through a durable personal loop: inspiration -> brainstorm -> PRD -> spec -> code -> tests -> personal validation -> feedback -> archive.

Use It For

• The user has a rough idea and needs the right workflow.
• The user asks which skill to use next.
• The user wants one repeatable process across product, code, and skill work.
• The user wants to turn loose input into a staged plan with clear gates.
• The user wants a closed loop that keeps updating the spec until personal validation passes.

Operating Rules

• Prefer the shortest chain that still reduces risk.
• Use one primary skill per stage.
• Stop at gates when the next stage needs more evidence.
• Reuse existing skills instead of inventing new process steps.
• If the right path is unclear, ask sharper questions before executing.
• Treat the spec as the loop's control document after it exists.
• When personal validation finds a mismatch, update the spec before changing code again.

Routing Pattern

1. Capture inspiration documents or raw notes.
2. Brainstorm and grill the idea until the problem, user, and success criteria are clear.
3. Produce or update a PRD.
4. Produce or update a spec from the PRD.
5. Generate or modify code against the current spec.
6. Run TDD tests and regression checks.
7. Ask for personal validation when behavior or product judgment cannot be fully automated.
8. If validation diverges from expectation, write feedback into the spec and repeat from step 5.
9. Archive the final PRD, spec, test evidence, decisions, and implementation notes.

Skill Map

1. Frame

Use grill-me or grilling when the request is vague, contradictory, or high impact.
Use them again inside the loop when personal validation reveals unclear expectations.

2. Capture

Use writing-fragments when the user has raw notes, half-formed ideas, or scattered observations.
Use notion-mrd-prd when inspiration lives in Notion MRD documents.

3. Synthesize

Use notion-mrd-prd when the source of truth is Notion MRD notes and the goal is PRDs, specs, or SSD planning.
Use to-prd when the source is an existing conversation and the user wants a PRD without a Notion roundtrip.
Use request-refactor-plan when the request is a codebase refactor or staged cleanup.

4. Decompose

Use decision-mapping when the goal is broad and needs sequenced investigation tickets or implementation slices.

5. Build

Use implement when the user wants the code changed.
Use tdd before or during implementation when the work is risky, bug-prone, or needs regression discipline.

6. Verify

Use review after code changes or when the user explicitly wants a review.
Use diagnosing-bugs when something is broken, slow, or failing and the next step is root-cause analysis.
Use personal validation when the acceptance criteria require human product judgment.

7. Publish Skills

Use skill-creator when designing or updating a skill.
Use skillhub-publish when packaging, validating, or publishing a personal skill to SkillHub.

Good Workflow Shapes

• Inspiration docs -> grill-me -> notion-mrd-prd or to-prd -> spec -> implement -> tdd -> personal validation -> spec update loop -> archive
• Idea -> grill-me -> decision-mapping -> implement -> tdd -> personal validation -> review
• Notion MRDs -> notion-mrd-prd -> spec -> decision-mapping -> implement -> validation loop
• Refactor -> request-refactor-plan -> decision-mapping -> implement -> review
• Skill work -> skill-creator -> skillhub-publish

Validation Loop

When tests pass but the user says the result is not right:

1. Capture the mismatch as feedback.
2. Update the spec with the expected behavior, constraints, or examples.
3. Add or adjust TDD coverage when the mismatch is automatable.
4. Re-run implementation against the updated spec.
5. Repeat until personal validation passes.
6. Archive the final artifacts.

Do not treat user feedback as a one-off code tweak when it changes product intent. Reflect it in the spec first.

Archive Contents

Archive the finished workflow with:

• final PRD
• final spec
• implementation summary
• test and regression evidence
• personal validation notes
• unresolved follow-ups

Output Style

When routing, report:

• the chosen skill chain
• why each step is included
• what gate would stop the next step
• whether the workflow is inside the validation loop or ready to archive

Reference

Read references/skill-matrix.md for the detailed routing matrix.