You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/getting-started/tutorial-daily-standup-sprint-review.md
+20-9Lines changed: 20 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,12 @@ This tutorial walks you through a complete **daily standup and sprint review** w
20
20
- Use **`.specfact/backlog.yaml`** or environment variables when you're not in the repo (e.g. CI) or to override
21
21
-**Post a standup comment** to the first (or selected) item with `--yesterday`, `--today`, `--blockers` and `--post`
22
22
- Use **`--interactive`** for step-by-step story review (arrow-key selection, full detail, **existing comments on each issue** when the adapter supports them)
23
-
- Use **`--copilot-export <path>`** to write a Markdown summary for Copilot slash-command during standup
24
-
- 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**
23
+
- Use **`--copilot-export <path>`** to write a Markdown summary for Copilot slash-command during standup;
24
+
add **`--comments`** (alias **`--annotations`**) to include descriptions and comment annotations when
25
+
the adapter supports fetching comments
26
+
- Use **`--summarize`** or **`--summarize-to <path>`** to output a **prompt** (instruction + filter context
27
+
+ standup data) for a slash command (e.g. `specfact.daily`) or copy-paste to Copilot to **generate a
28
+
standup summary**; add **`--comments`**/**`--annotations`** to include comment annotations in the prompt
25
29
- 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)
26
30
- Filter by **`--assignee`**, **`--sprint`** / **`--iteration`**, **`--blockers-first`**, and optional **`--suggest-next`**
27
31
@@ -121,10 +125,13 @@ Use **`--suggest-next`** to show a suggested next item by value score (business
121
125
To feed a **summary file** into your AI IDE (e.g. for a Copilot slash-command during standup):
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.).
131
+
The file contains one section per item (ID, title, status, assignees, last updated, progress, blockers).
132
+
With `--comments`/`--annotations`, it also includes the item description and comment annotations when the
133
+
adapter supports fetching comments. You can open it in your IDE and use it with Copilot. Same scope as
134
+
the standup table (state, assignee, limit, etc.).
128
135
129
136
---
130
137
@@ -134,13 +141,17 @@ To get a **prompt** you can paste into Copilot or feed to a slash command (e.g.
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).
150
+
The output includes an instruction to generate a standup summary, the applied filter context (adapter,
151
+
state, sprint, assignee, limit), and the same per-item data as `--copilot-export`. With
152
+
`--comments`/`--annotations`, the prompt includes comment annotations when supported. Use it with the
153
+
**`specfact.backlog-daily`** slash prompt for interactive team walkthrough (story-by-story, current focus,
154
+
issues/open questions, discussion notes as comments).
144
155
145
156
---
146
157
@@ -187,8 +198,8 @@ The output includes an instruction to generate a standup summary, the applied fi
187
198
| 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`. |
188
199
| Post standup to first item | Use `--yesterday "..."``--today "..."``--blockers "..."` and `--post` (values required). |
189
200
| Step through stories with full detail (including issue comments) | Use `--interactive`; optionally `--suggest-next`. |
190
-
| Feed standup into Copilot | Use `--copilot-export <path>`. |
191
-
| Generate standup summary via AI (slash command or Copilot) | Use `--summarize` (stdout) or `--summarize-to <path>`; use with `specfact.backlog-daily` slash prompt. |
201
+
| Feed standup into Copilot | Use `--copilot-export <path>`; add `--comments`/`--annotations` for comment annotations. |
202
+
| 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. |
-**Definition of Ready (DoR)**: Automatic validation of story readiness for sprint planning
16
16
-**Backlog Refinement** 🆕: AI-assisted template-driven refinement for standardizing work items from DevOps backlogs
17
-
- **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.
17
+
-**Daily Standup**: Use `specfact backlog daily <adapter>` to list my/filtered items with status and last activity.
18
+
Default scope (state=open, limit=20, optional assignee=me) is applied when not overridden; configure via
19
+
`SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`, `SPECFACT_STANDUP_ASSIGNEE` or
20
+
`.specfact/standup.yaml`. Use `--iteration` / `--sprint` (e.g. `--sprint current`) to focus on current
21
+
iteration when the adapter supports it; sprint/iteration end date is shown when provided by adapter or
22
+
config (`standup.sprint_end_date`). A second table **Pending / open for commitment** lists unassigned
23
+
items (same scope); use `--show-unassigned`/`--no-show-unassigned` or `--unassigned-only`. Use
24
+
`--blockers-first` to sort items with blockers first; enable `show_priority` or `show_value` in standup
25
+
config for optional priority/value column (value-driven/SAFe). Optional standup summary
26
+
(yesterday/today/blockers) from item body; optionally post standup comment to linked issue via `--post`
27
+
when the adapter supports comments (e.g. GitHub).
28
+
**Interactive step-by-step review**: Use `--interactive` to select stories with arrow keys (questionary)
29
+
and view full detail (refine-like: description, acceptance criteria, standup fields, comments when adapter
30
+
supports); navigate with Next/Previous/Back to list/Exit. Use `--suggest-next` to show suggested next
31
+
item by value score (business_value / (story_points × priority)).
32
+
**Copilot export**: Use `--copilot-export <path>` to write a summarized Markdown file of each story for
33
+
Copilot. Add `--comments` (alias `--annotations`) to include descriptions and comment annotations in
34
+
`--copilot-export` and `--summarize` outputs when the adapter supports `get_comments` (GitHub).
35
+
**Kanban**: omit iteration/sprint and use state + limit; unassigned = pullable work. **Scrum/SAFe**: use
36
+
`--sprint current` and optional priority/value. **Out of scope**: Sprint goal is in your board/sprint
37
+
settings (not displayed by CLI). Stale/at-risk flags (e.g. "no update in N days") are not in scope—use
38
+
last updated + blockers. Structured "blocked by" (link to another issue) is not in scope; only free-text
39
+
blockers are supported.
18
40
-**Dependency Management**: Track story-to-story and feature-to-feature dependencies
19
41
-**Prioritization**: Priority levels, ranking, and business value scoring
20
42
-**Sprint Planning**: Target sprint/release assignment and story point tracking
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.
87
+
Use the **`specfact.backlog-daily`** (or `specfact.daily`) slash prompt for interactive walkthrough with the
88
+
DevOps team story-by-story (current focus, issues/open questions, discussion notes as comments). Default
89
+
scope: **state=open**, **limit=20**; configure via `SPECFACT_STANDUP_*` or `.specfact/standup.yaml`. Use
-**Issue Creation**: Export OpenSpec change proposals as GitHub Issues (or other DevOps backlog items)
21
21
-**Progress Tracking**: Automatically detect code changes and add progress comments to issues
22
-
- **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.
22
+
-**Standup Comments**: Use `specfact backlog daily --post` with `--yesterday`, `--today`, `--blockers` to post
23
+
a standup summary as a comment on the linked issue (GitHub/ADO adapters that support comments). Standup
24
+
config: set defaults via env (`SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`,
25
+
`SPECFACT_STANDUP_ASSIGNEE`, `SPECFACT_STANDUP_SPRINT_END`) or optional `.specfact/standup.yaml`
26
+
(e.g. `default_state`, `limit`, `sprint`, `show_priority`, `suggest_next`). Iteration/sprint and sprint
27
+
end date support depend on the adapter (ADO supports current iteration and iteration path; see adapter
28
+
docs). Use `--blockers-first` and config `show_priority`/`show_value` for time-critical and value-driven
29
+
standups. **Interactive review** (`--interactive`): step-through stories with arrow-key selection; detail
30
+
view shows **existing comments annotated to each issue** when the adapter implements `get_comments(item)`
0 commit comments