feat(automation): preserve gated roadmap queue and source prompts

2026-10-29 14:21:59 +01:00
parent 5032ccb415
commit 4da3939547
81 changed files with 14524 additions and 0 deletions
@@ -0,0 +1,25 @@
+We've completed the initial discovery and design interview.
+
+Review the approved preferences and decision register.
+
+Now begin Round One of the Jobbjakt visual design workshop.
+
+Generate five genuinely distinct designs: A1, B1, C1, D1 and E1.
+
+Each must include a realistic dashboard, navigation, optional onboarding state, mobile adaptation and light/dark themes.
+
+Build them in the isolated design lab so I can compare actual rendered interfaces.
+
+Use identical sample data across concepts.
+
+Do not generate five near-identical layouts.
+
+Explain what makes each design different, its advantages and disadvantages, and which elements you personally recommend.
+
+Provide the local URL, screenshots and clear comparison instructions.
+
+When finished, ask me up to five focused questions about my favourite designs and individual components.
+
+STOP for my feedback.
+
+Do not begin the next iteration or modify the production UI.
@@ -0,0 +1,31 @@
+Continue our Jobbjakt iterative design workshop.
+
+I've reviewed the current mockups.
+
+My preferences are:
+
+- Favourite overall design:
+- Favourite sidebar/navigation:
+- Favourite dashboard layout:
+- Favourite typography:
+- Favourite colours:
+- Favourite tables and lists:
+- Favourite mobile navigation:
+- Elements I dislike:
+- Other changes I want:
+
+Use my answers together with all previous feedback and approved design decisions.
+
+Do not change elements I've explicitly approved unless there is a clear accessibility or consistency issue, in which case explain the issue first.
+
+Generate three new coherent design variations combining my selected components.
+
+Preserve earlier versions and record the new iteration.
+
+Show desktop/mobile and light/dark comparisons.
+
+Explain the tradeoffs and make a recommendation.
+
+Ask me 3–5 targeted questions about what to keep, change or explore next.
+
+STOP after presenting the new designs. Do not implement the production redesign.
@@ -0,0 +1,35 @@
+I'm provisionally happy with the visual direction we've developed.
+
+Do not begin production implementation yet.
+
+Expand the selected design into a complete, coherent Jobbjakt product experience.
+
+Design and prototype the three primary journeys:
+
+1. Dashboard-first, guided but optional onboarding.
+2. Everyday job discovery, application management, follow-ups and interviews.
+3. CV creation, editing, job-specific tailoring, AI assistance and export.
+
+Also cover settings, automation controls, navigation, error recovery and important secondary screens.
+
+For each major journey:
+
+- Identify and remove unnecessary friction.
+- Reuse information rather than requiring repeated entry.
+- Provide contextual next actions.
+- Demonstrate individual automation controls.
+- Make mobile equally capable and usable as desktop.
+- Maintain English/Norwegian and light/dark support.
+- Target WCAG 2.2 AA.
+- Preserve consistent visual design.
+- Provide realistic interactive prototypes.
+
+Show me alternative workflows wherever meaningful design choices remain unresolved.
+
+Ask targeted questions about those choices and explain your recommendations.
+
+Document current journeys, improved journeys, design decisions and implementation implications.
+
+When the prototypes are complete, present a complete design approval package and STOP.
+
+Do not begin the full production redesign until I explicitly approve it.
@@ -0,0 +1,33 @@
+I explicitly approve the final Jobbjakt design package and the agreed user journeys.
+
+Proceed with the approved production implementation plan.
+
+First verify the current branch, implementation baseline, previous decisions, and unresolved release blockers.
+
+Implement the approved design incrementally, starting with shared foundations and proceeding through all major product areas.
+
+Preserve existing functionality, user data, security boundaries and integrations.
+
+For each phase:
+
+- Implement the approved changes.
+- Update shared components and tests.
+- Verify mobile and desktop.
+- Verify English and Norwegian.
+- Verify light and dark themes.
+- Run relevant accessibility and regression checks.
+- Capture before/after screenshots.
+- Document completed work and unresolved issues.
+- Present important changes for review.
+
+Do not introduce unapproved visual directions or product features.
+
+Do not weaken failing tests or silently defer defects.
+
+Keep all production changes on an isolated development branch.
+
+Do not merge, push or deploy without explicit approval.
+
+Once the entire implementation is finished and reviewed, prepare the application for full release-readiness qualification.
+
+Do not declare production readiness based solely on the completed redesign.
@@ -0,0 +1,41 @@
+Begin Jobbjakt's comprehensive final release-readiness qualification.
+
+This includes the complete frontend, backend, database, AI services, integrations, authentication, infrastructure, security, accessibility, user journeys and CI/CD.
+
+Review the approved design package, implementation acceptance evidence and all historical release blockers.
+
+Perform fresh, evidence-backed qualification of:
+
+1. All functional user journeys.
+2. Mobile and desktop usability.
+3. WCAG 2.2 AA accessibility.
+4. Authentication, authorization and cross-user data isolation.
+5. Security vulnerabilities and dependencies.
+6. MariaDB integration, migrations and data integrity.
+7. Linux PDF generation and document fidelity.
+8. AI integrations and failure handling.
+9. Email and OAuth integrations.
+10. Performance and reliability.
+11. Docker and production configuration.
+12. CI/CD and hosted runner qualification.
+13. Backup, restore and rollback.
+14. Monitoring, logging and operational readiness.
+15. Documentation and deployment procedures.
+
+Reassess previously documented blockers, including PDF fidelity, Python dependency advisories, hosted MariaDB CI and runner isolation.
+
+Use authorized isolated environments for active security testing and deployment rehearsals.
+
+Reproduce findings, implement safe focused fixes, add regression coverage and requalify affected areas.
+
+Record PASS, FAIL, BLOCKED or NOT TESTED for every gate.
+
+Do not fabricate verification results or count historical passes as fresh evidence.
+
+Produce a complete release acceptance matrix, remediation register, deployment runbook and final GO / CONDITIONAL GO / NO-GO report.
+
+If a mandatory gate cannot be verified, report it transparently.
+
+Do not merge, publish, deploy, change live infrastructure or execute production migrations without my explicit permission.
+
+Complete as much actual qualification and remediation as the available environment and permissions allow, rather than stopping at a checklist.