fraim 2.0.362-next.4 → 2.0.362

package/dist/registry/stubs/jobs/ai-employee/product/process-interview-notes.md

@@ -0,0 +1,42 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: process-interview-notes
+
+## Intent
+Extract, structure, and analyze customer insights from raw interview notes, transcript, or recording from a **single** customer interview. Produce one consolidated artifact containing the analysis, the personalized follow-up email, and a local quality summary in YAML frontmatter that the founder (and the holistic `review-customer-development` job) read to coach interview *technique*. Portfolio-level customer-development scoring is owned by `review-customer-development`.
+
+## Outcome
+- **Reviewable deliverable**: a .docx review copy generated from the interview artifact via the author-docx skill at submission; this is the outcome delivered for review, with the .md below as the canonical agent-side record.
+- **Single artifact**: `docs/customer-development/interviews/[customer-name-slug]-interview.md`. When `interview-preparation` ran for this participant, this is the same file it created; this job adds the analysis so one file per customer covers prep, interview, and follow-up. The file contains:
+  1. **YAML frontmatter** at the very top with a `quality:` block (composite score, participant scores, evidence metrics, coaching note, interviewee, company, timestamp). The frontmatter is the human-readable summary of how this *one* interview went, consumed locally for technique coaching and read by `review-customer-development` as one input among many.
+  2. **Bottom Line Up Front** section.
+  3. **Participant Profile** with Fit / Urgency / Authority scores.
+  4. **Cleaned Signals** (chronological, with quotes).
+  5. **Extracted Insights** (tagged Pain Point / Feature Request / Workflow Gap / Praise).
+  6. **Quality Assessment** (quote-by-quote table, bias risk, notable absences).
+  7. **Validation** of any prep-doc hypotheses.
+  8. **Open Questions / Follow-Ups**.
+  9. **Follow-Up Email** as a `## Follow-Up Email Draft` section inside the same file. Do NOT write a separate follow-up file.
+  10. **Source Notes** (the raw input as provided, for traceability).
+
+## Steps
+1. Phase 1: `raw-input-processing`
+2. Phase 2: `single-session-insight-extraction`
+3. Phase 3: `participant-scoring`
+4. Phase 4: `conversation-quality-assessment`
+5. Phase 5: `artifact-generation`
+6. Phase 6: `artifact-submission`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "process-interview-notes" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/product/review-customer-development.md

@@ -0,0 +1,38 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: review-customer-development
+
+## Intent
+Holistically evaluate the founder's customer-development artifact set — prospect discovery, interview prep, participant recruitment, processed interview notes, user surveys, and triaged customer needs — and produce a portfolio-level quality score for the founder-journey quality dashboard. This job does not create customer-development artifacts; it reviews what exists and tells the founder how well the customer-development surface is actually being covered.
+
+## Outcome
+- **Reviewable deliverable**: a .pptx synthesis deck generated from the review artifact at submission; this is the outcome delivered for review, with the .md below as the canonical agent-side record.
+- **Final artifact**: `docs/customer-development/customer-development-quality-review.md`
+- **Quality Scores**: Flat sub-scores (0-10) for ICP coherence, interview coverage, evidence quality, pattern saturation, signal-to-product flow, and survey rigor.
+- **Composite Score**: Overall customer-development quality (0-10), emitted to `fraim_quality_scores`.
+- **Coaching**: Specific, actionable recommendations for the highest-impact improvements.
+- **Gap Analysis**: What's missing or weak across the customer-development artifact set.
+
+## Steps
+1. Phase 1: `artifact-discovery`
+2. Phase 2: `prospect-and-icp-review`
+3. Phase 3: `interview-coverage-review`
+4. Phase 4: `pattern-saturation-review`
+5. Phase 5: `signal-to-product-review`
+6. Phase 6: `cross-artifact-coherence`
+7. Phase 7: `quality-score-emission`
+8. Phase 8: `review-submission`
+9. Phase 9: `address-feedback`
+10. Phase 10: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "review-customer-development" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/product/send-newsletter.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: send-newsletter
+
+## Intent
+Draft a source-backed customer newsletter from recent product changes, submit audience and content for one review, and send only through the explicit post-approval send action.
+
+## Outcome
+- Final newsletter message: `docs/customer-development/newsletters/newsletter-<range>.html`
+- Recipient-level delivery statuses only after the manager selects `approve_and_send`
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `collect-issue-data`
+3. Phase 3: `draft-campaign`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "send-newsletter" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/product/send-thank-you-notes.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: send-thank-you-notes
+
+## Intent
+Find completed customer-reported issues, draft one source-backed thank-you note per reporter, and send only after explicit approval.
+
+## Outcome
+- Final reviewable thank-you HTML drafts (the actual message deliverables), one file per verified recipient, in `docs/customer-development/thank-you-notes/<date>-html/`
+- Recipient-level delivery statuses only after the manager selects `approve_and_send`
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `collect-issue-data`
+3. Phase 3: `draft-campaign`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "send-thank-you-notes" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/product/triage-customer-needs.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: triage-customer-needs
+
+## Intent
+Systematically review *multiple* interview analysis files to identify recurring patterns, cluster similar feedback, and prioritize development work based on aggregate evidence. This is the "Product Management" layer above the single "User Research" layer.
+
+## Outcome
+- **Reviewable deliverable**: a .docx review copy generated from the final artifact via the author-docx skill at submission; this is the outcome delivered for review, with the .md below as the canonical agent-side record.
+- Final artifact: `docs/customer-development/triage-customer-needs-{YYYY-MM-DD}.md`.
+- **Prioritized Backlog**: A ranked list of features/fixes derived from multiple customers.
+- **{{proxy.config.repository.provider | NO_OP | "Issue Tracker"}} Issues**: Concrete work items created or updated in the issue tracker.
+
+## Steps
+1. Phase 1: `cross-interview-synthesis`
+2. Phase 2: `validated-jtbd-synthesis`
+3. Phase 3: `evidence-gate-evaluation`
+4. Phase 4: `strategic-prioritization`
+5. Phase 5: `work-item-definition`
+6. Phase 6: `work-item-review`
+7. Phase 7: `work-item-filing`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "triage-customer-needs" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/project-management/cross-functional-dependency-management.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: cross-functional-dependency-management
+
+## Intent
+Produce a dependency map, blocker log, and escalation plan that make cross-team delivery risks actionable without mutating official systems before approval.
+
+## Outcome
+- **Reviewable deliverable**: `docs/delivery-ops/cross-functional-dependency-management-{YYYY-MM-DD}.docx`
+- Dependency map, owner gaps, blocker log, handoff criteria, and proposed escalations
+
+## Steps
+1. Phase 1: `dependency-discovery`
+2. Phase 2: `owner-mapping`
+3. Phase 3: `blocker-resolution`
+4. Phase 4: `handoff-coordination`
+5. Phase 5: `dependency-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "cross-functional-dependency-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/project-management/delivery-governance-review.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: delivery-governance-review
+
+## Intent
+Review delivery health and produce a source-backed governance brief with RAID state, milestone confidence, gaps, and escalation needs.
+
+## Outcome
+- **Reviewable deliverable**: `docs/delivery-ops/delivery-governance-review-{project}-{YYYY-MM-DD}.docx`
+- Normalized RAID log, milestone health summary, evidence highlights, and escalation recommendations
+
+## Steps
+1. Phase 1: `load-delivery-context`
+2. Phase 2: `normalize-raid-state`
+3. Phase 3: `produce-governance-brief`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "delivery-governance-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/project-management/operational-reporting.md

@@ -0,0 +1,37 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: operational-reporting
+
+## Intent
+Produce a reviewable operating, portfolio-impact, stakeholder-status, or security-posture report from normalized evidence using one explicit report mode: `weekly-operating-review`, `portfolio-impact`, `stakeholder-status`, or `security-posture`.
+
+## Outcome
+- **Reviewable deliverable**:
+  - `weekly-operating-review`: `docs/business-ops/operating-review-{YYYY-MM-DD}.pptx` or markdown brief with cash, pipeline, blockers, priorities, and required decisions.
+  - `portfolio-impact`: `docs/business-ops/portfolio-impact-report-{program}-{YYYY-MM-DD}.pptx` plus optional metrics CSV, evidence map, and founder-interview briefs.
+  - `stakeholder-status`: `docs/delivery-ops/stakeholder-status-reporting-{project-name}-{YYYY-MM-DD}.pptx` with executive summary, RAG-scored workstream table, and actions/decisions.
+  - `security-posture`: `docs/security/security-posture-{YYYY-MM-DD}.pptx` with a unified findings ledger, a RAG-scored exposure summary, a prioritized remediation queue, and a disposition trail, normalized from the project's issue tracker rather than re-derived from raw scans.
+- Evidence, assumptions, gaps, and report-mode constraints remain visible.
+- The job creates the report or deck. External recipient-specific sending remains the job of `send-stakeholder-update`.
+
+## Steps
+1. Phase 1: `load-reporting-context`
+2. Phase 2: `select-report-mode`
+3. Phase 3: `normalize-evidence`
+4. Phase 4: `score-health`
+5. Phase 5: `produce-report`
+6. Phase 6: `submit`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "operational-reporting" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/project-management/project-plan-creation.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: project-plan-creation
+
+## Intent
+Create a reviewable project plan with scope, dependencies, milestones, risks, and explicit gaps before the team makes delivery commitments.
+
+## Outcome
+- **Reviewable deliverable**: `docs/delivery-ops/project-plan-{project-name}-{YYYY-MM-DD}.docx`
+- Scope boundary, dependency map, milestone sequence, risk register, assumptions, and approval-needed actions
+
+## Steps
+1. Phase 1: `scope-intake`
+2. Phase 2: `dependency-mapping`
+3. Phase 3: `milestone-sequencing`
+4. Phase 4: `risk-register`
+5. Phase 5: `project-plan-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "project-plan-creation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/project-management/scrum-sprint-planning.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: scrum-sprint-planning
+
+## Intent
+Run a structured sprint planning process — from backlog grooming through capacity planning, sprint goal definition, and acceptance criteria review — so the team starts the sprint with a clear commitment, not a wish list.
+
+## Outcome
+- Final artifact: Sprint plan at `docs/delivery/sprints/{date}-sprint-{number}-plan.md`.
+- **Sprint Goal**: A single, measurable outcome statement that defines what the sprint delivers.
+- **Sprint Backlog**: A set of issues sized to team capacity with confirmed acceptance criteria.
+- **Capacity Plan**: Team velocity and availability factored into the committed work.
+
+## Steps
+1. Phase 1: `backlog-review`
+2. Phase 2: `capacity-planning`
+3. Phase 3: `sprint-goal-definition`
+4. Phase 4: `acceptance-criteria-review`
+5. Phase 5: `sprint-plan-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "scrum-sprint-planning" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/project-management/sprint-planning.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sprint-planning
+
+## Intent
+Turn a candidate backlog into a realistic sprint plan using WSJF-informed prioritization, explicit capacity limits, and a single sprint document the team can execute from.
+
+## Outcome
+- Final artifact: `docs/project-management/sprint-plan-{project}-{YYYY-MM-DD}.md`
+- A normalized backlog with WSJF scores and rationale
+- A committed sprint scope, stretch scope, and explicit not-in-sprint list
+- Dependency, risk, and assumption notes that make tradeoffs auditable
+
+## Steps
+1. Phase 1: `load-planning-context`
+2. Phase 2: `score-backlog`
+3. Phase 3: `shape-sprint`
+4. Phase 4: `produce-sprint-document`
+5. Phase 5: `submit`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sprint-planning" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/accessibility-audit.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: accessibility-audit
+
+## Intent
+Audit a web application against WCAG 2.1 AA criteria using automated scanning and manual testing, produce a severity-scored findings report, and deliver a prioritized remediation plan.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/quality-assurance/accessibility-audit-{YYYY-MM-DD}.docx with WCAG 2.1 AA Compliance Score, Severity-Scored Findings, and Remediation Plan sections.
+- **WCAG 2.1 AA Compliance Score**: Pass/fail/partial for each applicable success criterion.
+- **Severity-Scored Findings**: Each finding scored by severity (critical, serious, moderate, minor).
+- **Remediation Plan**: Prioritized fix list with implementation effort and WCAG criterion reference.
+
+## Steps
+1. Phase 1: `automated-scan`
+2. Phase 2: `manual-testing`
+3. Phase 3: `wcag-scoring`
+4. Phase 4: `remediation-plan`
+5. Phase 5: `accessibility-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "accessibility-audit" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/api-testing.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: api-testing
+
+## Intent
+Design and execute a comprehensive API test suite — from contract discovery through schema validation, invalid-request testing, and error scenario coverage — ensuring the API behaves correctly under expected, edge, and failure conditions. Use this job to verify API contracts and input handling; use the separate mutation-testing job to investigate whether tests detect source-code regressions.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/quality-assurance/api-testing-report-{YYYY-MM-DD}.docx with Contract Coverage, Schema Validation, Mutation Tests, and Error Scenario Coverage sections.
+- **Contract Coverage**: All endpoints documented and tested.
+- **Schema Validation**: Request and response schemas validated against the specification.
+- **Mutation Tests**: Invalid inputs tested and correct error responses confirmed.
+- **Error Scenario Coverage**: Authentication errors, rate limits, and downstream failures tested.
+
+## Steps
+1. Phase 1: `contract-discovery`
+2. Phase 2: `schema-validation`
+3. Phase 3: `mutation-testing`
+4. Phase 4: `error-scenario-coverage`
+5. Phase 5: `api-testing-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "api-testing" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/codebase-quality-assessment.md

@@ -0,0 +1,37 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: codebase-quality-assessment
+
+## Intent
+To perform a deep analysis of the codebase's implementation quality and pattern consistency, evaluating it against FRAIM's standards and generating one comprehensive health report with one prioritized remediation plan. Use it when the question is "How healthy is this codebase's implementation?" or "Is my codebase consistent enough for AI agents to keep working in?"
+
+This job merges what were previously two separate reviews of the same surface: general code quality (hardcoded values, duplication, monolithic files, complexity, architecture health) and "broken windows" - files that deviate from the codebase's dominant patterns and teach AI agents the wrong pattern. Both dimensions are scored, reported, and remediated together, once.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/quality-assurance/codebase-quality-report-{YYYY-MM-DD}.pptx with overall grade, multi-dimension review scorecards (code quality, broken windows/pattern consistency, type safety, error handling, architecture, maintainability), and one prioritized remediation plan.
+- **Graded Quality**: An overall grade (A-F) for the codebase.
+- **Multi-Dimension Review**: Explicit findings for code quality and broken windows/pattern consistency, in one review.
+- **One Remediation Plan**: A single prioritized plan covering both dimensions. This job detects and plans - it does not execute a fix. Use `code-refactoring`, `feature-implementation`, or `iterative-quality-improvement` to actually apply the plan's recommendations.
+
+## Steps
+1. Phase 1: `environment-check`
+2. Phase 2: `evaluate-codebase-quality`
+3. Phase 3: `remediation-planning`
+4. Phase 4: `author-quality-report`
+5. Phase 5: `review-findings`
+6. Phase 6: `quality-score-emission`
+7. Phase 7: `codebase-quality-submission`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "codebase-quality-assessment" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/iterative-quality-improvement.md

@@ -0,0 +1,37 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: iterative-quality-improvement
+
+## Intent
+To systematically improve application quality — including full-app behavior across browsers and devices — through iterative cycles of Review → Critique → Fix → Validate, ensuring high-quality, production-ready applications.
+
+Use this job for comprehensive quality improvement when applications need multiple rounds of review and fixes before meeting production standards, typically before major releases or after significant feature implementations. This is also the job for "keep testing and fixing my whole app until it's actually good" and end-to-end browser validation requests — a freestanding, whole-app pass, distinct from `ui-polish-validation`'s per-issue pixel/interaction check.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/quality-assurance/iterative-improvement-{YYYY-MM-DD}.pptx containing iteration cycle summaries, resolved issues dashboard, quality metrics tracking across cycles, and production readiness scorecard.
+- **Resolved Issues**: All identified issues are fixed and validated.
+- **Validated Application**: Confirmation of functionality across browsers, devices, and screen sizes.
+- **Production Readiness**: Application is stable, performs well, and provides a good user experience.
+
+## Steps
+1. Phase 1: `initial-review`
+2. Phase 2: `critique-and-issue-identification`
+3. Phase 3: `systematic-fixes`
+4. Phase 4: `validation`
+5. Phase 5: `iteration-decision`
+6. Phase 6: `documentation-and-handoff`
+7. Phase 7: `quality-submission`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "iterative-quality-improvement" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/mutation-testing.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: mutation-testing
+
+## Intent
+Find where passing tests could miss regressions, so the manager can prioritize improvements to test protection. Use this job for a scoped test-strength investigation, including when no prior test-authoring assessment exists.
+
+## Outcome
+- A PowerPoint report explaining which behavior the tests protect, the material gaps and uncertainty, and the recommended next actions.
+- Supporting evidence that lets the reviewer trace the findings and understand the investigation's limits.
+
+## Steps
+1. Phase 1: `mutation-scoping`
+2. Phase 2: `mutation-run`
+3. Phase 3: `mutation-report`
+4. Phase 4: `mutation-submission`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "mutation-testing" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/performance-quality-assessment.md

@@ -0,0 +1,38 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: performance-quality-assessment
+
+## Intent
+Produce a graded, product-wide performance quality review — memory efficiency, CPU efficiency, disk I/O, and startup cost — the way `codebase-quality-assessment` does for code. Use it when the question is "is this app efficient, independent of traffic?", not "does it hold up under production traffic?" (`stress-test-app-under-load`).
+
+The dividing line: if you need to generate traffic to see the problem, it is `stress-test-app-under-load`. If the problem is there even at zero concurrent users, it is this job. `stress-test-app-under-load` drives a synthetic load generator at an HTTP-facing app and reports user-experienced latency percentiles under load. This job takes any running process — web app, desktop app, CLI, or background service — and measures its own memory/CPU/disk footprint over natural, observed operation with zero traffic generation, tracing every finding to a confirmed root cause in source.
+
+## Outcome
+- **Reviewable deliverable**: A report at `docs/quality-assurance/performance-quality-report-{YYYY-MM-DD}.md` with an overall A-F grade, a dimension scorecard, evidence highlights, and a prioritized remediation plan.
+- **Graded Quality**: An overall grade (A-F) for the target's runtime efficiency.
+- **Dimension Scorecard**: Scored `memoryEfficiency`, `cpuEfficiency`, `diskIO`, and `startupCost`, each with a rationale citing a specific live measurement and source location.
+- **Prioritized Remediation**: A remediation list ordered by severity, each item naming the dimension it improves, a complexity rating (High / Medium / Low) with rationale, and the confirmed root cause.
+- **Dashboard Telemetry**: A row in `fraim_quality_scores`, rendered as a new "Performance Quality" tile on the Quality dashboard, tracked run-over-run alongside Code Quality, UI/UX Quality, Test Quality, and Production Readiness.
+- **Filed Work Items**: Every confirmed finding gets a prioritized, prepared post-submit issue record. Filing happens only when the manager selects the approval-gated filing action at submit — this job diagnoses, scores, and prepares; it does not implement fixes and does not file anything unreviewed.
+
+## Steps
+1. Phase 1: `environment-check`
+2. Phase 2: `live-performance-profiling`
+3. Phase 3: `score-performance-dimensions`
+4. Phase 4: `remediation-planning`
+5. Phase 5: `author-quality-report`
+6. Phase 6: `performance-quality-submission`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "performance-quality-assessment" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/quality-assurance/stress-test-app-under-load.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: stress-test-app-under-load
+
+## Intent
+Establish performance baselines, run load testing at realistic traffic levels, analyze Core Web Vitals, and produce a threshold-based performance report with actionable optimization recommendations.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/quality-assurance/stress-test-app-under-load-{YYYY-MM-DD}.pptx with baseline metrics (P50/P95/P99 latencies), load test results dashboard, Core Web Vitals assessment, and optimization recommendations with impact scoring.
+- **Baseline Metrics**: Current performance at normal load — P50, P95, P99 latency and error rate per endpoint.
+- **Load Test Results**: Performance under target peak load with failure thresholds identified.
+- **Core Web Vitals Assessment**: LCP, INP, CLS scores for key user-facing pages.
+- **Optimization Recommendations**: Prioritized performance improvements with expected impact.
+
+## Steps
+1. Phase 1: `baseline-measurement`
+2. Phase 2: `load-testing`
+3. Phase 3: `cwv-analysis`
+4. Phase 4: `threshold-reporting`
+5. Phase 5: `performance-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "stress-test-app-under-load" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.