yknothing/prodcraft

1

ci-cd Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when bro…

yknothing/prodcraft

7

2

code-review Use when a concrete code change is ready for review and the reviewer must evaluate correctness, security, maintainabi…

yknothing/prodcraft

7

3

deployment-strategy Use when a release candidate is ready and the team must choose the safest rollout pattern, verification checkpoints, …

yknothing/prodcraft

7

4

feature-development Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable impl…

yknothing/prodcraft

7

5

incident-response Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evide…

yknothing/prodcraft

7

6

intake The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-d…

yknothing/prodcraft

7

7

monitoring-observability Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose rea…

yknothing/prodcraft

7

8

observability Use when code, workflows, or AI execution paths need structured telemetry such as logs, metrics, traces, skill-invoca…

yknothing/prodcraft

7

9

problem-framing Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-…

yknothing/prodcraft

7

10

prodcraft Use when software-development work is underway or likely, so the task routes through the Prodcraft lifecycle-aware en…

yknothing/prodcraft

7

11

requirements-engineering Use when the work is still at the “what should we build” stage and approved discovery inputs or entry-stack outputs m…

yknothing/prodcraft

7

12

security-audit Use when a reviewed change, release candidate, or high-risk slice must be challenged for abuse paths, trust-boundary …

yknothing/prodcraft

7

13

system-design Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, componen…

yknothing/prodcraft

7

14

task-breakdown Use when reviewed architecture or API contracts must be decomposed into implementation-ready work items, especially w…

yknothing/prodcraft

7

15

tdd Use when a reviewed task is ready for implementation and the team must drive the work by writing failing tests first,…

yknothing/prodcraft

7

16

acceptance-criteria Use when defining testable criteria that determine whether a requirement is met

yknothing/prodcraft

4

17

accessibility Use when a user interface, user-facing flow, or acceptance criteria need accessibility requirements, audits, or remed…

yknothing/prodcraft

4

18

api-design Use when architecture boundaries are already defined and the team must specify stable API contracts between component…

yknothing/prodcraft

4

19

data-modeling Use when the system structure is known and the team must turn domain concepts and architectural boundaries into durab…

yknothing/prodcraft

4

20

delivery-completion Use when verified implementation work must be merged, handed off through a PR, preserved for later, or explicitly dis…

yknothing/prodcraft

4

21

documentation Use when a feature, architecture decision, incident, or workflow change needs durable technical documentation such as…

yknothing/prodcraft

4

22

domain-modeling Use when reviewed requirements still carry ambiguous business nouns, overlapping concepts, or possible bounded contex…

yknothing/prodcraft

4

23

e2e-scenario-design Use when designing or implementing E2E tests that need to go beyond shallow happy-path flows — especially for multi-s…

yknothing/prodcraft

4

24

estimation Use when reviewed tasks exist and the team must size them with explicit assumptions, confidence, and risk awareness b…

yknothing/prodcraft

4

25

receiving-code-review Use when review feedback has arrived and the author must verify, sequence, and respond to comments without blind agre…

yknothing/prodcraft

4

26

refactoring Use when existing code is correct but structurally costly to change, and the team needs to improve clarity, coupling,…

yknothing/prodcraft

4

27

release-management Use when a tested release candidate needs a coordinated go/no-go decision, release window, communication path, and ow…

yknothing/prodcraft

4

28

retrospective Use when a sprint, release, or incident has ended and the team needs to turn evidence about what worked, what failed,…

yknothing/prodcraft

4

29

risk-assessment Use when planned work must be challenged for delivery, dependency, migration, security, or operational risk before th…

yknothing/prodcraft

4

30

runbooks Use when an operational task or incident needs a concrete step-by-step procedure that another responder can execute s…

yknothing/prodcraft

4

31

security-design Use when the architecture is defined and the team must turn trust boundaries, sensitive data paths, and attacker assu…

yknothing/prodcraft

4

32

spec-writing Use when reviewed requirements need a shared product or technical specification that fixes scope, non-goals, interfac…

yknothing/prodcraft

4

33

sprint-planning Use when the team has sized work and must choose a realistic iteration scope, sequence, and ownership model that fits…

yknothing/prodcraft

4

34

systematic-debugging Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code …

yknothing/prodcraft

4

35

task-execution Use when an approved task slice already exists and the team needs a 2-5 minute execution plan with checkpoints, stop …

yknothing/prodcraft

4

36

tech-debt-management Use when repeated findings from reviews, incidents, retrospectives, or delivery friction need to be turned into a pri…

yknothing/prodcraft

4

37

tech-selection Use when the architecture is known and the team must choose concrete languages, frameworks, data stores, or infrastru…

yknothing/prodcraft

4

38

testing-strategy Use when a reviewed implementation slice or feature needs a deliberate test plan across unit, integration, contract, …

yknothing/prodcraft

4

39

user-research Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-…

yknothing/prodcraft

4

40

verification-before-completion Use when about to claim a phase, fix, task, build, or release is complete, fixed, passing, or ready for handoff and f…

yknothing/prodcraft

4

41

feasibility-study Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision base…

yknothing/prodcraft

2

42

bug-history-retrieval Use when a current bug, incident, regression, or recurring symptom may match a known internal defect and the agent ne…

yknothing/prodcraft

1

43

compliance Use when legal, contractual, regulatory, or internal policy requirements must be translated into engineering constrai…

yknothing/prodcraft

1

44

implementation-alignment-review Use after implementation or repair work when the reviewer must judge intent realization, requirement coverage, scope …

yknothing/prodcraft

1

45

implementation-integrity-audit Use after code changes when the reviewer must aggressively audit low-level defects, deceptive implementations, improp…

yknothing/prodcraft

1

46

internationalization Use when user-facing text, locale-sensitive formatting, or multi-language behavior need explicit rules so copy, layou…

yknothing/prodcraft

1

47

market-analysis Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a n…

yknothing/prodcraft

1

48

pc-estimation Use when reviewed tasks exist and the team must size them with explicit assumptions, confidence, and risk awareness b…

yknothing/prodcraft

1