Build features/<f>/input/context-pack.md from Jira/Confluence MCP, local files, or chat. Run when user gives ticket keys, page ids, or says fetch context.
User provides: feature folder name features/<f>/, Jira key(s), optional Confluence pageId or space+title, optional existing-feature path or paste.
jira_get_issue, confluence_get_page / confluence_search_cql as needed.features/<f>/input/jira-context.md and/or confluence-context.md (optional raw).features/<f>/input/context-pack.md with fixed headings:
## Sources — bullets: Jira PROJ-123, Confluence id …## Goal — one paragraph max## Facts — bullets only; no HTML dump## Open questions — bullets for ambiguities to confirm with userexisting-feature.md into ## Facts / with a pointer line.## Existing behaviordraft-feature-summary.Tight bullets; cite keys; long bodies stay in optional raw side files only.
After writing context-pack.md, write/update features/<f>/.konie-state.yml:
phase: fetchcheckpoints.context_confirmed: false (user has not confirmed yet)summary: one line describing what was fetched