v2: Forge Console + Open WebUI artifacts + Docker

- web/: Local chat UI (Express + WS → Codex bridge)
- openwebui/: Preset, pipelines, knowledge manifest
- Dockerfile + docker-compose.yml
- Updated README with 3 frontend options
- CLI-agnostic: works with Codex, Claude Code, Kiro, Gemini

skills/epics-standards/references/aha-epic-workflow.md

@@ -0,0 +1,55 @@
+# Aha Epic Workflow
+
+This file captures the expected Aha epic lifecycle and downstream triggers.
+
+## Idea Management
+
+1. Customer submits idea in Aha.
+2. Check voting threshold: `5` unique orgs.
+3. PM review required (`Needs Review` -> `Reviewed`).
+4. PM decision:
+- Accept current release -> `Planned`
+- Accept next release -> `Future Consideration`
+- Exists -> `Already Exists`
+- Need more info -> `Needs More Info` + comment
+- Reject/later -> `Future Consideration` + comment
+5. Always add public customer comment after decision.
+6. Ensure epic relation:
+- Promote idea to new epic, or
+- Link idea to existing epic.
+
+## Epic Creation and Management
+
+When epic exists in Aha, fill mandatory fields:
+- Summary with PRD linkage
+- Release and availability (`Preview`/`GA`)
+- Confidence level (`High`/`Med`/`Low`)
+- Product type and persona
+- Execution team and initiative
+- Product lead, engineering lead, UX lead
+
+Set required flags and trigger follow-ups:
+- `Doc Required = Yes` -> specify doc type and doc-team flow
+- `Provisioning = Yes` -> PCC/Olga flow
+- `UI/UX Required = Yes` -> engage UX
+- `Security Review = Yes` -> engage security
+- `Training Required = Yes` -> engage training
+
+Integration:
+- Ensure Aha -> Jira Webhooks 2.0 integration path is respected.
+- Ensure Jira epic has `Aha! Reference`.
+
+## Enablement Outputs
+
+If applicable, drive enablement:
+- Technical enablement session (config)
+- GTM/sales enablement artifacts
+- Webinar for major highlights
+
+Template links from workflow:
+- Technical Enablement Session template:
+  `https://docs.google.com/presentation/d/1fCZhOUSV7McX1edmYoKBHYtKnYajykbm1U2N5aJ1j-M/edit?slide=id.g39258ed0d71_0_442`
+- Value Statements input template:
+  `https://docs.google.com/document/d/1YEquYIjt8gMtGLf8EJFfvwS0f_ij1KuIfQFOjlcOEjI/edit`
+- Sales Enablement deck example:
+  `https://docs.google.com/presentation/d/1mIlC3OhhQgdwcFPgJ328pm1oQl5W6y-w/edit`

skills/epics-standards/references/epic-fields-checklist.md

@@ -0,0 +1,53 @@
+# RP Epic Field Checklist
+
+Standard page:
+`https://reltio.jira.com/wiki/spaces/PM/pages/2688385025/PM+Standards+Epics`
+
+Use this checklist during epic create/update.
+
+## Core fields
+
+- `Summary` (short Jira shorthand)
+- `Description` (business outcome + impact)
+- `Type of Effort`
+- `Fix Version` (or `N/A` when not yet planned)
+- `Status`
+
+## Product narrative fields
+
+- Problem Statement / Why
+- Solution / What
+- Persona / Who
+- Value Statement
+
+## Planning and delivery fields
+
+- Confidence Level
+- Path to Green (required when Confidence is Medium/Low for must-have epics)
+- Availability in Release
+- Planned Release
+- T-Shirt Size
+- Tier
+- Initiative
+
+## Ownership and dependencies
+
+- Product Lead
+- Engineering Lead
+- UX Lead
+- Execution Team
+- Execution Team Dependency
+
+## Go-to-market and governance
+
+- For documentation tickets: set `Affected Documentation` to a documentation target (for example `Help Portal`) and never `No`
+- Doc Required
+- Pricing Required
+- Security Review Required
+- Does this change PCC?
+- Tags (including `Must Have` when applicable)
+- Demo Link (when available)
+
+## Integration check
+
+- `Aha! Reference` is present and linked through the RP integration path.