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
This commit is contained in:
55
skills/epics-standards/references/aha-epic-workflow.md
Normal file
55
skills/epics-standards/references/aha-epic-workflow.md
Normal file
@@ -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`
|
||||
Reference in New Issue
Block a user