# Phase 7: Main Session Skill - Discussion Log

> **Audit trail only.** Do not use as input to planning, research, or execution agents.
> Decisions are captured in CONTEXT.md — this log preserves the alternatives considered.

**Date:** 2026-06-14
**Phase:** 7-Main Session Skill
**Areas discussed:** Session start behavior, Jira integration, Confluence docs, Session-end behavior

---

## Session Start Behavior

**User's choice:** Auto-check hindsight for similar sessions (<2 weeks). Jira ticket creation should prompt. Doc loading should prompt — docs need to search.

**Notes:** Three-tier behavior — similar sessions (auto), Jira (prompt), docs (prompt + search by tag).

---

## Jira Integration

**User's choice:** Always create Task type. Default board configurable later. Query available epics and cache in long-term memory — fetch occasionally or when asked.

**Notes:** Epic cache lives in hindsight memory. Don't fetch epics every session — use cached version, refresh on demand.

---

## Confluence Doc Search

**User's choice:** Create a tag for ngn-agent. Search Confluence by that tag and do matching.

**Notes:** Tag name TBD (default: `ngn-agent`). Present matching pages, user selects which to load.

---

## Session-End Behavior

**User's choice:** Always ask before Jira/Confluence updates. Always save session to hindsight (no prompt).

**Notes:** Session save is automatic. Jira comment and Confluence update are prompted.

---

## the agent's Discretion

- Exact tag name for Confluence searches
- Epic cache refresh interval
- Similar session display format

## Deferred Ideas

- Daily reporting cron (Phase 8)
- Stale session archive (Phase 8)
- Auto-create Jira tickets (user wants manual control)