Issue 179 resolution

CHANGELOG.md

@@ -9,6 +9,20 @@ All notable changes to this project will be documented in this file.
 
 ---
 
+## [0.26.17] - 2026-02-03
+
+### Fixed (0.26.17)
+
+- **Daily standup exports: comment annotations** (fixes [#179](https://github.com/nold-ai/specfact-cli/issues/179))
+  - **`--comments` / `--annotations`**: Include item descriptions and comment annotations in `--copilot-export` and
+    `--summarize`/`--summarize-to` outputs when the adapter supports `get_comments` (GitHub).
+  - **Docs**: Updated daily standup tutorial and guides to document the new flags and outputs.
+
+### Changed (0.26.17)
+
+- **Version**: Bumped to 0.26.17 for issue [#179](https://github.com/nold-ai/specfact-cli/issues/179)
+
+---
 ## [0.26.16] - 2026-02-02
 
 ### Added (0.26.16)

docs/getting-started/tutorial-daily-standup-sprint-review.md

@@ -20,8 +20,12 @@ This tutorial walks you through a complete **daily standup and sprint review** w
 - Use **`.specfact/backlog.yaml`** or environment variables when you're not in the repo (e.g. CI) or to override
 - **Post a standup comment** to the first (or selected) item with `--yesterday`, `--today`, `--blockers` and `--post`
 - Use **`--interactive`** for step-by-step story review (arrow-key selection, full detail, **existing comments on each issue** when the adapter supports them)
-- Use **`--copilot-export <path>`** to write a Markdown summary for Copilot slash-command during standup
-- Use **`--summarize`** or **`--summarize-to <path>`** to output a **prompt** (instruction + filter context + standup data) for a slash command (e.g. `specfact.daily`) or copy-paste to Copilot to **generate a standup summary**
+- Use **`--copilot-export <path>`** to write a Markdown summary for Copilot slash-command during standup;
+  add **`--comments`** (alias **`--annotations`**) to include descriptions and comment annotations when
+  the adapter supports fetching comments
+- Use **`--summarize`** or **`--summarize-to <path>`** to output a **prompt** (instruction + filter context
+  + standup data) for a slash command (e.g. `specfact.daily`) or copy-paste to Copilot to **generate a
+  standup summary**; add **`--comments`**/**`--annotations`** to include comment annotations in the prompt
 - Use the **`specfact.backlog-daily`** (or `specfact.daily`) slash prompt for interactive walkthrough with the DevOps team story-by-story (focus, issues, open questions, discussion notes as comments)
 - Filter by **`--assignee`**, **`--sprint`** / **`--iteration`**, **`--blockers-first`**, and optional **`--suggest-next`**
 
@@ -121,10 +125,13 @@ Use **`--suggest-next`** to show a suggested next item by value score (business
 To feed a **summary file** into your AI IDE (e.g. for a Copilot slash-command during standup):
 
 ```bash
-specfact backlog daily github --copilot-export ./standup-summary.md
+specfact backlog daily github --copilot-export ./standup-summary.md --comments
 ```
 
-The file contains one section per item (ID, title, status, assignees, last updated, progress, blockers). You can open it in your IDE and use it with Copilot. Same scope as the standup table (state, assignee, limit, etc.).
+The file contains one section per item (ID, title, status, assignees, last updated, progress, blockers).
+With `--comments`/`--annotations`, it also includes the item description and comment annotations when the
+adapter supports fetching comments. You can open it in your IDE and use it with Copilot. Same scope as
+the standup table (state, assignee, limit, etc.).
 
 ---
 
@@ -134,13 +141,17 @@ To get a **prompt** you can paste into Copilot or feed to a slash command (e.g.
 
 ```bash
 # Print prompt to stdout (copy-paste to Copilot)
-specfact backlog daily github --summarize
+specfact backlog daily github --summarize --comments
 
 # Write prompt to a file (e.g. for slash command)
-specfact backlog daily github --summarize-to ./standup-prompt.md
+specfact backlog daily github --summarize-to ./standup-prompt.md --comments
 ```
 
-The output includes an instruction to generate a standup summary, the applied filter context (adapter, state, sprint, assignee, limit), and the same per-item data as `--copilot-export`. Use it with the **`specfact.backlog-daily`** slash prompt for interactive team walkthrough (story-by-story, current focus, issues/open questions, discussion notes as comments).
+The output includes an instruction to generate a standup summary, the applied filter context (adapter,
+state, sprint, assignee, limit), and the same per-item data as `--copilot-export`. With
+`--comments`/`--annotations`, the prompt includes comment annotations when supported. Use it with the
+**`specfact.backlog-daily`** slash prompt for interactive team walkthrough (story-by-story, current focus,
+issues/open questions, discussion notes as comments).
 
 ---
 
@@ -187,8 +198,8 @@ The output includes an instruction to generate a standup summary, the applied fi
 | Override or use outside repo | Use `.specfact/backlog.yaml`, env vars (`SPECFACT_GITHUB_REPO_OWNER`, etc.), or CLI `--repo-owner`/`--repo-name` or `--ado-org`/`--ado-project`. |
 | Post standup to first item | Use `--yesterday "..."` `--today "..."` `--blockers "..."` and `--post` (values required). |
 | Step through stories with full detail (including issue comments) | Use `--interactive`; optionally `--suggest-next`. |
-| Feed standup into Copilot | Use `--copilot-export <path>`. |
-| Generate standup summary via AI (slash command or Copilot) | Use `--summarize` (stdout) or `--summarize-to <path>`; use with `specfact.backlog-daily` slash prompt. |
+| Feed standup into Copilot | Use `--copilot-export <path>`; add `--comments`/`--annotations` for comment annotations. |
+| Generate standup summary via AI (slash command or Copilot) | Use `--summarize` (stdout) or `--summarize-to <path>`; add `--comments`/`--annotations` for comment annotations; use with `specfact.backlog-daily` slash prompt. |
 
 ---
 

docs/guides/agile-scrum-workflows.md

@@ -14,7 +14,29 @@ SpecFact CLI supports real-world agile/scrum practices through:
 
 - **Definition of Ready (DoR)**: Automatic validation of story readiness for sprint planning
 - **Backlog Refinement** 🆕: AI-assisted template-driven refinement for standardizing work items from DevOps backlogs
-- **Daily Standup**: Use `specfact backlog daily <adapter>` to list my/filtered items with status and last activity. Default scope (state=open, limit=20, optional assignee=me) is applied when not overridden; configure via `SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`, `SPECFACT_STANDUP_ASSIGNEE` or `.specfact/standup.yaml`. Use `--iteration` / `--sprint` (e.g. `--sprint current`) to focus on current iteration when the adapter supports it; sprint/iteration end date is shown when provided by adapter or config (`standup.sprint_end_date`). A second table **Pending / open for commitment** lists unassigned items (same scope); use `--show-unassigned`/`--no-show-unassigned` or `--unassigned-only`. Use `--blockers-first` to sort items with blockers first; enable `show_priority` or `show_value` in standup config for optional priority/value column (value-driven/SAFe). Optional standup summary (yesterday/today/blockers) from item body; optionally post standup comment to linked issue via `--post` when the adapter supports comments (e.g. GitHub). **Interactive step-by-step review**: Use `--interactive` to select stories with arrow keys (questionary) and view full detail (refine-like: description, acceptance criteria, standup fields, comments when adapter supports); navigate with Next/Previous/Back to list/Exit. Use `--suggest-next` to show suggested next item by value score (business_value / (story_points × priority)). **Copilot export**: Use `--copilot-export <path>` to write a summarized Markdown file of each story for use with Copilot slash-command during standup (complementary aid, not replacement for backlog). **Kanban**: omit iteration/sprint and use state + limit; unassigned = pullable work. **Scrum/SAFe**: use `--sprint current` and optional priority/value. **Out of scope**: Sprint goal is in your board/sprint settings (not displayed by CLI). Stale/at-risk flags (e.g. "no update in N days") are not in scope—use last updated + blockers. Structured "blocked by" (link to another issue) is not in scope; only free-text blockers are supported.
+- **Daily Standup**: Use `specfact backlog daily <adapter>` to list my/filtered items with status and last activity.
+  Default scope (state=open, limit=20, optional assignee=me) is applied when not overridden; configure via
+  `SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`, `SPECFACT_STANDUP_ASSIGNEE` or
+  `.specfact/standup.yaml`. Use `--iteration` / `--sprint` (e.g. `--sprint current`) to focus on current
+  iteration when the adapter supports it; sprint/iteration end date is shown when provided by adapter or
+  config (`standup.sprint_end_date`). A second table **Pending / open for commitment** lists unassigned
+  items (same scope); use `--show-unassigned`/`--no-show-unassigned` or `--unassigned-only`. Use
+  `--blockers-first` to sort items with blockers first; enable `show_priority` or `show_value` in standup
+  config for optional priority/value column (value-driven/SAFe). Optional standup summary
+  (yesterday/today/blockers) from item body; optionally post standup comment to linked issue via `--post`
+  when the adapter supports comments (e.g. GitHub).
+  **Interactive step-by-step review**: Use `--interactive` to select stories with arrow keys (questionary)
+  and view full detail (refine-like: description, acceptance criteria, standup fields, comments when adapter
+  supports); navigate with Next/Previous/Back to list/Exit. Use `--suggest-next` to show suggested next
+  item by value score (business_value / (story_points × priority)).
+  **Copilot export**: Use `--copilot-export <path>` to write a summarized Markdown file of each story for
+  Copilot. Add `--comments` (alias `--annotations`) to include descriptions and comment annotations in
+  `--copilot-export` and `--summarize` outputs when the adapter supports `get_comments` (GitHub).
+  **Kanban**: omit iteration/sprint and use state + limit; unassigned = pullable work. **Scrum/SAFe**: use
+  `--sprint current` and optional priority/value. **Out of scope**: Sprint goal is in your board/sprint
+  settings (not displayed by CLI). Stale/at-risk flags (e.g. "no update in N days") are not in scope—use
+  last updated + blockers. Structured "blocked by" (link to another issue) is not in scope; only free-text
+  blockers are supported.
 - **Dependency Management**: Track story-to-story and feature-to-feature dependencies
 - **Prioritization**: Priority levels, ranking, and business value scoring
 - **Sprint Planning**: Target sprint/release assignment and story point tracking
@@ -56,13 +78,19 @@ specfact backlog daily github \
 # 4. Optional: interactive step-through, Copilot export, or standup summary prompt
 specfact backlog daily github --interactive   # step-through; detail view shows existing comments on each issue
 # or
-specfact backlog daily github --copilot-export ./standup.md
+specfact backlog daily github --copilot-export ./standup.md --comments
 # or
-specfact backlog daily github --summarize     # prompt to stdout for AI to generate standup summary
+specfact backlog daily github --summarize --comments     # prompt to stdout for AI to generate standup summary
 specfact backlog daily github --summarize-to ./standup-prompt.md
 ```
 
-Use the **`specfact.backlog-daily`** (or `specfact.daily`) slash prompt for interactive walkthrough with the DevOps team story-by-story (current focus, issues/open questions, discussion notes as comments). Default scope: **state=open**, **limit=20**; configure via `SPECFACT_STANDUP_*` or `.specfact/standup.yaml`. Use `--assignee me`, `--sprint current`, `--blockers-first`, `--interactive`, `--suggest-next`, `--copilot-export <path>`, `--summarize`, and `--summarize-to <path>` as needed. See [Tutorial: Daily Standup and Sprint Review](../getting-started/tutorial-daily-standup-sprint-review.md) for the full walkthrough.
+Use the **`specfact.backlog-daily`** (or `specfact.daily`) slash prompt for interactive walkthrough with the
+DevOps team story-by-story (current focus, issues/open questions, discussion notes as comments). Default
+scope: **state=open**, **limit=20**; configure via `SPECFACT_STANDUP_*` or `.specfact/standup.yaml`. Use
+`--assignee me`, `--sprint current`, `--blockers-first`, `--interactive`, `--suggest-next`,
+`--copilot-export <path>`, `--summarize`, `--summarize-to <path>`, and `--comments`/`--annotations` as
+needed. See [Tutorial: Daily Standup and Sprint Review](../getting-started/tutorial-daily-standup-sprint-review.md)
+for the full walkthrough.
 
 ## Persona-Based Workflows
 

docs/guides/devops-adapter-integration.md

@@ -19,7 +19,26 @@ SpecFact CLI supports **bidirectional synchronization** between OpenSpec change
 
 - **Issue Creation**: Export OpenSpec change proposals as GitHub Issues (or other DevOps backlog items)
 - **Progress Tracking**: Automatically detect code changes and add progress comments to issues
-- **Standup Comments**: Use `specfact backlog daily --post` with `--yesterday`, `--today`, `--blockers` to post a standup summary as a comment on the linked issue (GitHub/ADO adapters that support comments). Standup config: set defaults via env (`SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`, `SPECFACT_STANDUP_ASSIGNEE`, `SPECFACT_STANDUP_SPRINT_END`) or optional `.specfact/standup.yaml` (e.g. `default_state`, `limit`, `sprint`, `show_priority`, `suggest_next`). Iteration/sprint and sprint end date support depend on the adapter (ADO supports current iteration and iteration path; see adapter docs). Use `--blockers-first` and config `show_priority`/`show_value` for time-critical and value-driven standups. **Interactive review** (`--interactive`): step-through stories with arrow-key selection; detail view shows **existing comments annotated to each issue** when the adapter implements `get_comments(item)` (GitHub adapter supports it). **Value score / suggested next**: when BacklogItem has `story_points`, `business_value`, and `priority`, use `--suggest-next` or config `suggest_next` to show suggested next item (business_value / (story_points × priority)). **Standup summary prompt** (`--summarize` or `--summarize-to PATH`): output a prompt (instruction + filter context + standup data) for slash command or Copilot to generate a standup summary. **Slash prompt** `specfact.backlog-daily` (or `specfact.daily`): use with IDE/Copilot for interactive team walkthrough story-by-story (current focus, issues/open questions, discussion notes as comments); prompt file at `resources/prompts/specfact.backlog-daily.md`. **Sprint goal** is stored in your board/sprint settings and is not displayed or edited by the CLI.
+- **Standup Comments**: Use `specfact backlog daily --post` with `--yesterday`, `--today`, `--blockers` to post
+  a standup summary as a comment on the linked issue (GitHub/ADO adapters that support comments). Standup
+  config: set defaults via env (`SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`,
+  `SPECFACT_STANDUP_ASSIGNEE`, `SPECFACT_STANDUP_SPRINT_END`) or optional `.specfact/standup.yaml`
+  (e.g. `default_state`, `limit`, `sprint`, `show_priority`, `suggest_next`). Iteration/sprint and sprint
+  end date support depend on the adapter (ADO supports current iteration and iteration path; see adapter
+  docs). Use `--blockers-first` and config `show_priority`/`show_value` for time-critical and value-driven
+  standups. **Interactive review** (`--interactive`): step-through stories with arrow-key selection; detail
+  view shows **existing comments annotated to each issue** when the adapter implements `get_comments(item)`
+  (GitHub adapter supports it). **Comment annotations in exports**: add `--comments` (alias
+  `--annotations`) to include descriptions and comment annotations in `--copilot-export` and
+  `--summarize`/`--summarize-to` outputs when the adapter supports fetching comments. **Value score /
+  suggested next**: when BacklogItem has `story_points`, `business_value`, and `priority`, use
+  `--suggest-next` or config `suggest_next` to show suggested next item (business_value / (story_points ×
+  priority)). **Standup summary prompt** (`--summarize` or `--summarize-to PATH`): output a prompt
+  (instruction + filter context + standup data) for slash command or Copilot to generate a standup summary.
+  **Slash prompt** `specfact.backlog-daily` (or `specfact.daily`): use with IDE/Copilot for interactive
+  team walkthrough story-by-story (current focus, issues/open questions, discussion notes as comments);
+  prompt file at `resources/prompts/specfact.backlog-daily.md`. **Sprint goal** is stored in your
+  board/sprint settings and is not displayed or edited by the CLI.
 - **Content Sanitization**: Protect internal information when syncing to public repositories
 - **Separate Repository Support**: Handle cases where OpenSpec proposals and source code are in different repositories