Activities

Everything NABS Confidence 0.14.9 lets you do, in one list. There are 69 activities, grouped by the part of a retro they belong to. Each one says how to start it, what you should see, and which commands and settings it uses. How well each is tested is on the Test coverage and confidence page.

This page is built from the same catalogue as the coverage page, and a check fails if a command, setting, chat command or tool of the extension is missing from it.

Set up and settings

Starting the extension in a repository and changing how it behaves.

Start in a repository

Medium Test coverage

Open a folder (ideally a Git repository) and click the NABS rocket in the Activity Bar.

How to start: The Retros view; the Open Folder link in its welcome text.
What you should see: The Retros view lists your retros, or says there are none. Retros are stored in the retros folder (team/retros by default), created the first time you make a retro.
Settings: nabsConfidence.retrosFolder

Change settings in the Settings panel

Medium Test coverage

Open the Settings panel, choose whether to save to the workspace or to your user settings, edit values, reset one to its default.

How to start: NABS Confidence: Settings; the gear in the Retros view.
What you should see: Only the values you changed are written to the chosen settings file. Wrong values are explained in the panel instead of being saved.
Commands: Settings (nabsConfidence.openSettings)

Home

The landing page: where you start and where you come back to.

Open Home

Medium Test coverage

Open Home from the Retros view, or let it open by itself when the Retros view opens and nothing else is open.

How to start: NABS Confidence: Open Home; the Home button in the Retros view; opens by itself (once per window).
What you should see: Home shows Objectives and New Retro side by side. With no retros, Open Retro Dashboard opens Home too.
Commands: Open Home (nabsConfidence.openHome)
Settings: nabsConfidence.home.openAutomatically

Review objectives from Home

Medium Test coverage

See each open objective with when it was last assessed, the verdict, and a Needs review flag; open or assess it.

How to start: Home, Objectives column (Open and Assess buttons).
What you should see: An objective not assessed in the latest retro, or not assessed for longer than the review window, is flagged. Assess opens the Objective Assessment panel.
Settings: nabsConfidence.home.reviewAfterDays

Start the next retro from Home

Medium Test coverage

See the latest retro and its stage, continue it, or start the suggested next retro.

How to start: Home, Retros column (Continue and Start the next retro).
What you should see: The next retro starts the day after the last period ended and covers the same open objectives. Continue opens that retro on its dashboard.

Read the maturity curve and the empty states

Medium Test coverage

Read the retrospective maturity curve (Ritual, Reflection, Realignment, Reinvention); see what to do when there are no objectives, retros, GitHub remote or Copilot.

How to start: Home.
What you should see: Empty states say what is missing and what to do. The curve follows the light and dark themes.

New Retro and templates

Creating a retro, and choosing, sharing and writing feedback templates.

Create a retro

Medium Test coverage

Fill in the New Retro form: date, period, title, facilitator, feedback template, objectives, and whether to use GitHub and Copilot.

How to start: NABS Confidence: New Retro; the + button in the Retros view; Home.
What you should see: A dated Markdown retro is written under the retros folder with the Git insights for the period, the previous retro's action items carried forward, and the chosen objectives. The period continues from the previous retro. Mistakes are shown next to the field and nothing is created.
Commands: New Retro (nabsConfidence.newRetro)
Settings: nabsConfidence.defaultPeriodDays, nabsConfidence.facilitator

Choose a feedback template for the retro

Medium Test coverage

Pick a feedback template on New Retro (or change it in Prepare before anyone adds feedback). The form shows the template's description and its feedback types.

How to start: New Retro form, Feedback template; dashboard Prepare; Retro panel Details.
What you should see: The template is stored in the retro, so later changes to the default never rewrite old retros. The Add Feedback form offers that template's types.
Settings: nabsConfidence.defaultFeedbackTemplate

Use the built-in templates

Medium Test coverage

Use one of the eight built-in templates (Went well / Didn't go well, Mad / Sad / Glad, Start / Stop / Continue, 4Ls, Incident review, Pre-spective, Team health check, Customer interview), or your own in the feedbackTemplates setting.

How to start: New Retro form; the feedbackTemplates setting.
What you should see: Each template sets the feedback types, ratings, the headings used when summarising, the questions for the team and extra guidance for Copilot. The incident review has a five-whys prompt; the health check has ratings and an optional trend.
Settings: nabsConfidence.feedbackTemplates

Use templates from the repository and a shared template repository

Medium Test coverage Needs GitHub

Keep template folders in the retros folder, and/or point the shared templates setting at your team's template repository. Choose which source wins with the template sources setting.

How to start: Settings panel; nabsConfidence.templateSources and nabsConfidence.sharedTemplates.
What you should see: Templates from every source appear in New Retro, the first source in the list wins a clash, a recent cache avoids asking GitHub again, the cache keeps working offline, and a failing source is skipped without breaking the others.
Settings: nabsConfidence.templateSources, nabsConfidence.sharedTemplates

Create a new feedback template

Medium Test coverage

Name a template and choose what to start from (blank or a copy of an existing one); the template folder is created in the repository.

How to start: NABS Confidence: New Feedback Template…; the Settings panel, Feedback templates.
What you should see: A template folder with template.json (and retro.md) is created and opened; a duplicate or invalid id is refused.
Commands: New Feedback Template... (nabsConfidence.newTemplate)

Refresh feedback templates

Medium Test coverage Needs GitHub

Force a refresh of the shared templates.

How to start: NABS Confidence: Refresh Feedback Templates; the Settings panel.
What you should see: The shared templates are fetched again with a conditional request; "not modified" keeps the cached files.
Commands: Refresh Feedback Templates (nabsConfidence.refreshTemplates)

Get help while editing a template file

Low Test coverage

Edit template.json or templates.json and get completion, hover help and error squiggles.

How to start: VS Code's JSON editor (a JSON schema ships with the extension).
What you should see: The shipped schema agrees with the validator the extension uses.

Customise the retro document layout

Medium Test coverage

Open the retro layout template and edit the headings and sections future retros use.

How to start: NABS Confidence: Customise Template; the Retros view ... menu.
What you should see: The layout file is created if it is missing and opened; future retros use it, and placeholders you drop are left out.
Commands: Customise Template (nabsConfidence.customiseTemplate)

Use your own feedback types and entry format (older settings)

Medium Test coverage

Keep feedback types in the deprecated feedbackTypes setting, or change how entries are written with the entry template.

How to start: Settings: nabsConfidence.feedbackTypes and nabsConfidence.feedbackEntryTemplate.
What you should see: The old types become a "custom" template; the entry template must contain {{text}} once and only known placeholders; entries with an unknown type still show as "other".
Settings: nabsConfidence.feedbackTypes, nabsConfidence.feedbackEntryTemplate

Gather and feedback

Everyone adds feedback in their own time, then the facilitator moves the retro on.

Add feedback

Medium Test coverage

Open the Add Feedback form, pick a type from the retro's template, write the feedback, optionally rate it, link it to an objective, or make it anonymous. Add one, or add another.

How to start: NABS Confidence: Add Feedback…; the speech-bubble button on a retro; the dashboard's Gather stage; the Retro panel.
What you should see: The entry is written to your own feedback file with your Git name, or to the shared file when anonymous. Invalid input is rejected in the form and again by the extension.
Commands: Add Feedback... (nabsConfidence.addFeedback)

Write to your own file (per-person files)

Medium Test coverage

Add feedback; it lands in a file with your name. Switch to one shared file if you prefer.

How to start: nabsConfidence.feedbackFiles (perPerson, the default, or shared).
What you should see: Each person has their own Markdown file in the retro's feedback folder, so nobody edits anyone else's. The Retros view, Summarise and Copilot read all the files together.
Settings: nabsConfidence.feedbackFiles

Say you are done

Medium Test coverage

Mark your feedback done (or not done) when you have said what you want to say.

How to start: I'm Done on the Add Feedback form, the dashboard and the Retro panel; your name in the Retros view; NABS Confidence: Mark My Feedback as Done / Not Done.
What you should see: Your file records the status and when. The facilitator sees you as done. You can still add entries until feedback is locked.
Commands: Mark My Feedback as Done (nabsConfidence.markFeedbackDone), Mark My Feedback as Not Done (nabsConfidence.markFeedbackNotDone)

Edit, delete or find a feedback entry

Medium Test coverage

Open an entry from the Retros view or the Retro panel, change its type, rating or text, or delete it; jump to it in the feedback file.

How to start: Click an entry in the Retros view; NABS Confidence: Edit Feedback Entry…; Show in Feedback File.
What you should see: The entry is changed in place in the file it lives in. If someone else changed it meanwhile, your save is refused instead of overwriting. Delete asks for confirmation first.
Commands: Edit Feedback Entry... (nabsConfidence.editFeedback), Show in Feedback File (nabsConfidence.revealFeedbackEntry)

Open the feedback file

Low Test coverage

Open the retro's feedback.

How to start: NABS Confidence: Open Feedback File.
What you should see: The retro's feedback opens in the Retro panel at Feedback.
Commands: Open Feedback File (nabsConfidence.openFeedback)

Gather as the facilitator: who is done, and nudges

Medium Test coverage

See each person as done, still adding or not started, with counts by feedback type; copy a nudge for one person or everyone still adding; copy the invitation.

How to start: Retro Dashboard, Gather stage, Facilitator view.
What you should see: The facilitator sees progress without reading anyone's words. A nudge is text copied to the clipboard to paste into Teams, Slack or email: the extension never sends it.

Gather as a participant

Medium Test coverage

See your own entries and how many people are done; add feedback and mark yourself done; you cannot move the retro on.

How to start: Retro Dashboard, Gather stage, Participant view (the Facilitator / Participant switch).
What you should see: Your part is a short checklist; other people's words are left for the meeting. This is a view, not a permission: the files are in Git.

Lock feedback by leaving Gather

Medium Test coverage

Move the retro past Gather (after the panel asks, Carry On or Stay Here); go back to Gather to unlock.

How to start: Retro Dashboard: Continue to Insights; Back to Gather (Unlocks Feedback).
What you should see: The retro records stage and feedback: locked. Adding, editing and deleting feedback are refused in the forms until you go back. I'm Done still works.

Retro Dashboard and Retro panel

The guided flow through a retro, and the panel for one retro's details.

Open the Retro Dashboard

Medium Test coverage

Open the dashboard for the latest retro, or choose one; it opens at the stage the retro is in.

How to start: NABS Confidence: Open Retro Dashboard; the dashboard button in the Retros view; Home; a retro in the tree.
What you should see: The six stages (Prepare, Gather, Insights, Objectives, Decide, Close & share) show where the retro is. With several retros, a picker asks which one.
Commands: Open Retro Dashboard (nabsConfidence.openDashboard)

Prepare the retro

Medium Test coverage

Check the retro is ready: objectives chosen, template, period, feedback invitation; change the template and objectives.

How to start: Retro Dashboard, Prepare.
What you should see: The checks say plainly what is missing. Moving on with something missing asks first (a soft gate) and never blocks.

Switch between Facilitator and Participant views

Medium Test coverage

Choose the view you want; the dashboard remembers it.

How to start: Retro Dashboard header.
What you should see: A participant sees a short checklist and no controls for moving the retro on. It is a view, not a permission.

Move through the later stages from the dashboard

Medium Test coverage

Continue from stage to stage. Prepare and Gather are guided; Insights, Objectives, Decide and Close & share show a checklist with buttons that open the Retro panel, Objective focus, action items or Archive.

How to start: Retro Dashboard, stage buttons.
What you should see: The stage and who moved it are saved in the retro. The later stages hand over to the other panels.

Read and edit a retro in the Retro panel

Medium Test coverage

Open one retro to see its details, feedback, insights, action items and objectives in one place; change the title, period, facilitator, template and status.

How to start: NABS Confidence: Open Retro; click a retro in the Retros view.
What you should see: Changes are written to the retro file; the panel refreshes when the file changes on disk.
Commands: Retro Details... (nabsConfidence.openRetroPanel), Open Retro... (nabsConfidence.openRetro)

Set the retro status

Medium Test coverage

Mark a retro as draft, in progress or complete.

How to start: NABS Confidence: Set Status…; the Retro panel.
What you should see: The status is written into the retro file and shown in the Retros view.
Commands: Set Status... (nabsConfidence.setStatus)

Keep what you have typed when the panel refreshes

Medium Test coverage

Type in a form, switch away, let the retro change on disk; your typing stays.

How to start: All the panels.
What you should see: Panels redraw without throwing away unsaved input and tell you when someone else changed the file.

Insights and summaries

What the repository did in the period, and a summary of what the team said.

Analyse Git activity for the period

Medium Test coverage

Fill the retro's Insights from the Git log for its period: commits, authors, churn and the files that changed most. Refresh it later.

How to start: NABS Confidence: Analyse / Refresh Insights; the Retro panel, Analysis; created automatically with a new retro.
What you should see: The Insights section between the markers is replaced; the rest of the retro is left alone. An empty period says so.
Commands: Analyse / Refresh Insights (nabsConfidence.refreshInsights)

Add GitHub issues, pull requests and discussions to the Insights

Medium Test coverage Needs GitHub

Include what was opened, merged, closed or discussed on GitHub during the period (needs a GitHub remote and a GitHub sign-in; switch off with includeGitHub).

How to start: Same as Git insights, when includeGitHub is on.
What you should see: Insights shows the GitHub numbers, capped at 50 items per type; if GitHub is unavailable the Git insights are still written and the reason is logged.
Settings: nabsConfidence.includeGitHub

Summarise feedback without Copilot

Medium Test coverage

Fill the retro's feedback sections from the feedback entries when Copilot is switched off or not available.

How to start: NABS Confidence: Summarise Feedback into Retro; the Retro panel, Analysis; Use Copilot switched off.
What you should see: Entries are grouped under the template's headings with counts and the follow-up actions section; a modal asks before replacing sections you edited.
Commands: Summarise Feedback into Retro (nabsConfidence.summariseFeedback)
Settings: nabsConfidence.useAI

Summarise feedback with Copilot

Low Test coverage Needs Copilot

Ask Copilot to write the summary, themes and suggested action items from the feedback, focused on the retro's chosen objectives.

How to start: Same as above, with Use Copilot on and a Copilot model available.
What you should see: The feedback sections are filled by Copilot; if the answer is unusable the plain summary is written instead and the reason logged.
Settings: nabsConfidence.useAI, nabsConfidence.modelFamily

Keep working without Copilot or offline

Low Test coverage Needs Copilot

Everything that can work without Copilot or the network does: feedback, summaries, insights from Git, action items.

How to start: Automatic.
What you should see: With no Copilot model, or Use Copilot off, the plain paths are used and the extension says so in the log; with no network, cached templates are used and GitHub parts are skipped.
Settings: nabsConfidence.useAI

See release confidence in the retro's Insights

Medium Test coverage

Add a section "Release confidence since the last retro" to the retro's Insights, from the release reports saved in the repository: the score at the start and at the end of the period, how far it moved, and the activities whose level changed.

How to start: Automatic with a new retro; NABS Confidence Refresh Insights; the Retro panel, Analysis.
What you should see: The Insights block ends with the section. With no report in the period it says so and names the newest one; with one report it says there is no trend yet; a report saved before 0.14.4 has no levels, so it says the activities that moved are not known. A repository with no saved release report has no section. Retros asks the core for the sections; it never imports Releases.

Objectives

Longer-term objectives with acceptance criteria that retros check on.

Create and edit an objective

Medium Test coverage

Open the Objective form to write an objective: title, why it matters, status, target date, acceptance criteria and optional automatic measures.

How to start: NABS Confidence: New Objective…, Edit Objective…; the + in the Retros view's Objectives; Home.
What you should see: An objective file is written to the objectives folder; edits keep the rest of the file. Mistakes are shown inline and nothing is saved.
Commands: New Objective... (nabsConfidence.newObjective), Edit Objective... (nabsConfidence.editObjective)
Settings: nabsConfidence.objectivesFolder

Use GitHub issues as objectives

Medium Test coverage Needs GitHub

Label an issue as an objective (objectiveLabel) and list the repositories to read them from (objectiveSources); file objectives and issue objectives appear together.

How to start: Settings: objectiveSources, objectiveLabel; the Retros view.
What you should see: Issues with the label appear as objectives with their acceptance criteria; the first source wins a clash.
Settings: nabsConfidence.objectiveSources, nabsConfidence.objectiveLabel

Open an objective

Medium Test coverage

Open an objective's details from the Retros view, Home or a retro.

How to start: NABS Confidence: Open Objective; Show Objective in Retro.
What you should see: The objective opens in its panel (or its file, or its issue in the browser); Show Objective in Retro opens the retro at that objective.
Commands: Open Objective (nabsConfidence.openObjective), Show Objective in Retro (nabsConfidence.openRetroObjective)

Choose which objectives a retro focuses on

Medium Test coverage

Tick the objectives a retro looks at in New Retro and in Prepare; remove one (with confirmation if it has records).

How to start: New Retro form; dashboard Prepare; NABS Confidence: Choose Retro Objectives…
What you should see: Only the chosen objectives appear in the retro, its summaries and its prompts. Existing evidence, assessments and verdicts are kept verbatim; removing one that has records asks first. A retro with none says so.
Commands: Choose Retro Objectives... (nabsConfidence.relateObjectives)

Link feedback and action items to objectives

Medium Test coverage

Tag a feedback entry or an action item with an objective, so the objective shows what the team said and did about it.

How to start: Add Feedback form, Objective; #obj:<id> on an action item.
What you should see: The form only offers the retro's own objectives; entries and actions keep their objective when edited.

Add evidence and see automatic measures

Medium Test coverage

Record dated, signed evidence against an acceptance criterion; see measures worked out from the numbers (commits, pull requests, issues).

How to start: NABS Confidence: Add Objective Evidence…; Objective Assessment panel.
What you should see: Evidence is stored in the retro with your name and date; automatic measures are computed from the Insights numbers.
Commands: Add Objective Evidence... (nabsConfidence.addObjectiveEvidence)

Assess objectives with Copilot

Low Test coverage Needs Copilot

Ask Copilot to judge each chosen objective on the evidence in the retro: on track, at risk, off track or not enough evidence.

How to start: NABS Confidence: Assess Objectives with Copilot; the Objective Assessment panel.
What you should see: Each objective card shows the verdict, the reasoning and the evidence relied on; a bad answer is reported and nothing is overwritten.
Commands: Assess Objectives with Copilot (nabsConfidence.assessObjectives), Objective Assessment... (nabsConfidence.openObjectiveAssessment)
Settings: nabsConfidence.useAI, nabsConfidence.modelFamily

Record the team's verdict

Medium Test coverage

Record the team's verdict on an objective, agreeing with Copilot or overriding it with a reason.

How to start: NABS Confidence: Record Objective Verdict…; the Objective Assessment panel.
What you should see: The verdict, who recorded it and (for an override) the reason are written to the retro; Home and the Retros view show it.
Commands: Record Objective Verdict... (nabsConfidence.recordObjectiveVerdict)

Use release confidence as an objective measure

Medium Test coverage

Choose a release confidence measure (the newest score, how it moved, how many releases in a row reached 80, or the level of one activity of the catalogue) as the automatic measure of an objective's acceptance criterion, and have each retro show it from the saved release reports.

How to start: Objective form, Acceptance criteria, Automatic measure; (auto: release.confidence) or (auto: release.activity.<id>.level) in an objective file.
What you should see: The retro shows a line such as "Releases in a row at 80 or more - 3 releases in a row ... (from the release reports, <period>)" for the criterion. With no saved report in the period, or no catalogue, it says why instead of a number. A measure nobody provides is kept in the file and says so. An activity's level reads "Medium, 62 out of 100 (0.14.0 on 2026-10-10, commit abc1234); Low (40) on 0.13.0, now Medium". Retros and Releases never import each other.

Decide: action items

Turning what the team agreed into action items, and following them through.

Write and carry forward action items

Medium Test coverage

Write action items as a checklist in the retro, with @owners, due dates and issue links; the next retro lists what was left open and shows the follow-through rate.

How to start: The retro's Action items section; a new retro.
What you should see: Open items from the previous retro are copied forward (done ones are not); the follow-up section counts what was done.

Create GitHub issues for action items

Medium Test coverage Needs GitHub

Turn selected action items into GitHub issues (after a confirmation), labelled with the actionItemLabel.

How to start: NABS Confidence: Create GitHub Issues for Action Items…; the Retro panel, Action items.
What you should see: One issue per chosen item with a clean title and body; the retro line is rewritten with the link and the rest of the line kept.
Commands: Create GitHub Issues for Action Items... (nabsConfidence.createActionIssues)
Settings: nabsConfidence.actionItemLabel

Update action items from GitHub

Medium Test coverage Needs GitHub

Tick items off when their GitHub issue has been closed (and untick if reopened).

How to start: NABS Confidence: Update Action Items from GitHub; the Retro panel.
What you should see: Closed issues tick the matching lines; nothing else in the retro changes.
Commands: Update Action Items from GitHub (nabsConfidence.syncActionItems)

Open an action item

Low Test coverage Needs GitHub

Open the GitHub issue behind an action item.

How to start: NABS Confidence: Open Action Item; the Retros view.
What you should see: The issue opens in the browser.
Commands: Open Action Item (nabsConfidence.openActionItem)

Tag feedback and action items with a release activity

Medium Test coverage

Write `#act:<id>` in a feedback entry or an action item to link it to an activity of the release catalogue. The dashboard lists the activities that are tagged, with how many feedback entries and action items each has and its level in the newest saved release report. A GitHub issue made from the action item gets an activity:<id> label.

How to start: #act:<id> in the text of feedback or an action item; the Retro Dashboard, Release activities.
What you should see: The dashboard shows a "Release activities" table once anything is tagged, in every stage. An activity with no saved report shows why instead of a level. An id that is not an activity of the catalogue is listed with the reason. The issue title does not carry the tag.

Close and archive

Finishing a retro and keeping its record where the team can find it.

Check where the archive will go

Low Test coverage Needs GitHub

Open the Archive panel; it checks that the repository is on GitHub, Discussions are on and a Retro Archive category exists, with links to fix each.

How to start: NABS Confidence: Archive Retro to Discussion…; the retro's context menu; the dashboard's Close & share stage.
What you should see: The panel says what is missing and disables posting until it is fixed. Nothing is posted.
Commands: Archive Retro to Discussion... (nabsConfidence.archiveRetro)

Post the retro to a GitHub Discussion

Low Test coverage Needs GitHub

Preview and post the retro as one Discussion: the body, one comment per person, and parts for insights, objectives, decide and close; resume if interrupted; post again without duplicates.

How to start: Archive panel, Archive to Discussion.
What you should see: A Discussion is created in the Retro Archive category. Long parts are split. Posted parts are recognised by a marker, so resuming or running again never duplicates them.

Remove the archived files safely

Low Test coverage Needs GitHub

After the Discussion is posted, remove the retro's files from the working tree. This is refused until everything is committed and pushed.

How to start: Archive panel, Remove the files.
What you should see: Files are removed with Git so the history keeps them; the record comment says how to restore them. An unpushed change stops the removal.

Find archived retros

Low Test coverage Needs GitHub

See archived retros in the Retros view, open an archived retro's Discussion, and ask @retro about it.

How to start: The Retros view (Archived); NABS Confidence: Open Archived Retro's Discussion; @retro.
What you should see: The index of archived retros (newest first, one per date) is read back; bad entries are reported rather than thrown.
Commands: Open Archived Retro's Discussion (nabsConfidence.openArchivedRetro)

@retro chat and language model tools

Asking Copilot Chat about your retros.

Ask @retro in Copilot Chat

Low Test coverage Needs Copilot

Use @retro, /insights, /feedback and /objectives in Copilot Chat, or ask a free-form question about your retros.

How to start: Copilot Chat: @retro.
What you should see: The answer is written from your retros, the Git and GitHub activity and the retro's chosen objectives, in the chat. Without Copilot Chat the participant is not available.
Settings: nabsConfidence.modelFamily
Chat: nabs.retro, nabs.retro/insights, nabs.retro/feedback, nabs.retro/objectives

Let an agent read retros (#retros tools)

Medium Test coverage Needs Copilot

In Agent mode, let Copilot list retros, read a retro or its feedback, and summarise Git activity.

How to start: Copilot Chat Agent mode (#retros).
What you should see: The tools return data from the open repository; bad dates are refused with a clear message.
Tools: nabs_list_retros, nabs_read_retro, nabs_read_feedback, nabs_get_git_activity

Let an agent read GitHub activity

Low Test coverage Needs GitHub Needs Copilot

In Agent mode, let Copilot list issues, pull requests and discussions active in a date range.

How to start: Copilot Chat Agent mode (#retros).
What you should see: Returns the GitHub items for the period, as in the Insights.
Tools: nabs_get_github_activity

Diagnostics and the Retros view

Finding things, and reporting problems.

Report a problem

Medium Test coverage

Describe a problem in a form; the extension prefills a GitHub issue with your version, environment and recent log lines, or copies the report as Markdown.

How to start: NABS Confidence: Report a Problem…; the Retros view.
What you should see: A prefilled issue form opens in the browser (nothing is sent without you pressing Submit on GitHub). Long reports keep the link short by dropping the oldest log lines first.
Commands: Report a Problem... (nabsConfidence.reportProblem)

Read the log

Medium Test coverage

Open the NABS Confidence output channel to see what the extension did and why something fell back.

How to start: NABS Confidence: Show Log.
What you should see: The channel opens; it logs what happened.
Commands: Show Log (nabsConfidence.showLog)

Never get a top-of-window prompt

Medium Test coverage

Everything is done in forms and panels, never a Quick Pick or input box at the top of the window.

How to start: All commands.
What you should see: No command opens a Quick Pick or input box (a design rule for this extension).

Browse retros, feedback, objectives and archived retros in the Retros view

Medium Test coverage

See retros (with their status), the people and entries in each, the objectives and the archive, in the Activity Bar.

How to start: The NABS rocket in the Activity Bar; NABS Confidence: Refresh.
What you should see: The tree follows the files: it refreshes when they change, and a welcome message guides you when it is empty.
Commands: Refresh (nabsConfidence.refresh)

Release confidence

How sure we are that a release works, with the reasons, per activity and for the whole release.

Work out the release confidence score

Low Test coverage

Give every activity a score from 0 to 100 (unit tests 25, integration tests 25, a real-world run 50, less open gaps, with caps), the release a score weighted by impact, and a verdict (Hold, Go with known risks, Go), each with the reasons in plain words and what would raise it.

How to start: npm run release:score (add --explain for every activity). The engine is in src/modules/release/score and the evidence builder in src/modules/release/evidence; the numbers are in catalogue/catalogue.yml. The Release dashboard (rel-dashboard) shows it; the report comes later.
What you should see: Each activity and the release has a score, a level and a sentence that says why, and the gates (a failed test, a high-impact activity that is Low, a changed file that belongs to no activity) hold the release.

See what changed since the last release

Low Test coverage

Read which files changed since the last release (a tag or a commit), say which activities own them, which shared code they touch (and so which activities it puts at risk), and which changes belong to nobody.

How to start: The change reader in src/modules/release/changes; the dashboard shows it under Changed since the last release.
What you should see: Every changed file is classified as an activity's own code, shared code, not code under test, or unowned. An unowned change is reported and holds the release.

Record test results and real-world runs against a commit

Low Test coverage

Turn a test run (the unit tests here, a CI run later) into a result file tagged with the commit and whether the working tree was dirty, so results for another commit count as not run; and build the record of a real-world run (who, which commit, which steps passed or failed).

How to start: npm run release:record-tests (writes .nabs/results/unit.json); CI saves the unit and integration results of each commit as the artifact test-results-<sha>; the Record a real-world run form (its own activity, rel-record-form) writes catalogue/runs/manual-<version>-<date>.yml.
What you should see: A result file that reads back the same, evidence per activity from fresh results only, and a run record that passes the run schema whatever is typed into it.

See the release confidence dashboard

Medium Test coverage

Open a dashboard that shows the release verdict and score with the reason in plain words, what holds the release back, every activity with its score, level, where the score comes from and what would raise it, what changed since the last release, and the real-world runs; run the tests that record the result; show a line about it in Home and in the view.

How to start: NABS Confidence: Release Confidence; the shield button in the view title; the Release Confidence node in the view; the card on Home; the Run the Tests button (npm run release:record-tests in a terminal).
What you should see: The dashboard shows the same score as npm run release:score, with the gates, the per-activity explanations and the changed code. In a folder with no catalogue it says what is missing instead of a score, and Home and the view show nothing.
Commands: Release Confidence (nabsConfidence.release.open), Run the Release Tests (nabsConfidence.release.runTests)
Settings: nabsConfidence.release.since, nabsConfidence.release.unknownRunCredit, nabsConfidence.release.writtenGaps

Record a real-world run in a form

Medium Test coverage

Fill in who ran which steps of the manual test script, on which commit, with the tracking issue and a summary, and write the run record that the release score uses as real-world evidence.

How to start: NABS Confidence: Record a Real-World Run...; the Record a Real-World Run button on the dashboard.
What you should see: A run record is written to catalogue/runs/manual-<version>-<date>.yml with exactly the steps that were run, and the dashboard counts it at once. A bad form, or a run that already exists, writes nothing and says why.
Commands: Record a Real-World Run... (nabsConfidence.release.recordRun)

Share the release report

Low Test coverage Needs GitHub

Turn the release confidence score into a report in Markdown that states the commit, what it is based on and every reason in plain words; copy it, save it in the repository (the history of the score), copy a one-line badge, or post it as a GitHub Discussion after choosing a category and confirming in the form.

How to start: NABS Confidence: Release Report...; the Report button on the Release Confidence dashboard.
What you should see: The report shows the same score as the dashboard, says how to read it, lists every activity with its reasons, and fits a Discussion. A saved report is never overwritten and does not make the test results stale. Nothing is posted without a category, a title and the ticked confirmation, and the same report is never posted twice.
Commands: Release Report... (nabsConfidence.release.report)

Check, score and list gaps of any repository from the command line

Low Test coverage

Scaffold a catalogue with init, run the catalogue check, the Release Confidence score, the list of gaps and the recording of test results on any repository that has a catalogue/ folder, without npm, TypeScript or VS Code. It reads C# and TypeScript test names, TRX, JUnit XML and Mocha JSON results, takes the version from package.json or from a file named in catalogue.yml, and needs no copy of the schemas. The dashboard reads the same result files, and catalogue.yml can name the command its Run the Tests button runs.

How to start: node dist/catalogue-cli.js init, check, score, gaps or record-tests with --repo <path> (built by npm run compile from src/cli/catalogue.ts), or nabs-catalogue from the npm package that npm run package:cli builds.
What you should see: A repository with only a catalogue/ folder, its tests and a test result file gets the same check and score report as this one.

Tag issues by activity and turn catalogue gaps into issues

Low Test coverage

Reads the activity ids a person or a Retro action item put on an issue or Discussion, in a hidden catalogue marker or in the Activities field of the issue form, and gives the item the catalogue:<group> labels. It can also open one issue for every activity that has a gap text, with a stable gap id, and never opens the same gap twice, high impact first, or only the gaps named with --only. Both are a dry run until --apply.

How to start: node dist/catalogue-cli.js labels or gap-issues with --repo <path> and --github owner/repo; --apply to write, --limit n for the number of new issues.
What you should see: A team can filter its issues and Discussions by the part of the product they are about, and every written gap has one issue that is found again by its marker and not by its title.

Every command

All commands the extension adds to VS Code, and the activity each belongs to. Search for the name in the Command Palette.

Command	Id	Activity
Open Home	`nabsConfidence.openHome`	Open Home
New Retro	`nabsConfidence.newRetro`	Create a retro
Open Retro Dashboard	`nabsConfidence.openDashboard`	Open the Retro Dashboard
Release Confidence	`nabsConfidence.release.open`	See the release confidence dashboard
Record a Real-World Run...	`nabsConfidence.release.recordRun`	Record a real-world run in a form
Release Report...	`nabsConfidence.release.report`	Share the release report
Run the Release Tests	`nabsConfidence.release.runTests`	See the release confidence dashboard
Retro Details...	`nabsConfidence.openRetroPanel`	Read and edit a retro in the Retro panel
Open Retro...	`nabsConfidence.openRetro`	Read and edit a retro in the Retro panel
Add Feedback...	`nabsConfidence.addFeedback`	Add feedback
Open Feedback File	`nabsConfidence.openFeedback`	Open the feedback file
Analyse / Refresh Insights	`nabsConfidence.refreshInsights`	Analyse Git activity for the period
Summarise Feedback into Retro	`nabsConfidence.summariseFeedback`	Summarise feedback without Copilot
Set Status...	`nabsConfidence.setStatus`	Set the retro status
Customise Template	`nabsConfidence.customiseTemplate`	Customise the retro document layout
Refresh	`nabsConfidence.refresh`	Browse retros, feedback, objectives and archived retros in the Retros view
Settings	`nabsConfidence.openSettings`	Change settings in the Settings panel
Report a Problem...	`nabsConfidence.reportProblem`	Report a problem
Show Log	`nabsConfidence.showLog`	Read the log
Edit Feedback Entry...	`nabsConfidence.editFeedback`	Edit, delete or find a feedback entry
Show in Feedback File	`nabsConfidence.revealFeedbackEntry`	Edit, delete or find a feedback entry
Mark My Feedback as Done	`nabsConfidence.markFeedbackDone`	Say you are done
Mark My Feedback as Not Done	`nabsConfidence.markFeedbackNotDone`	Say you are done
Create GitHub Issues for Action Items...	`nabsConfidence.createActionIssues`	Create GitHub issues for action items
Update Action Items from GitHub	`nabsConfidence.syncActionItems`	Update action items from GitHub
Open Action Item	`nabsConfidence.openActionItem`	Open an action item
New Feedback Template...	`nabsConfidence.newTemplate`	Create a new feedback template
Refresh Feedback Templates	`nabsConfidence.refreshTemplates`	Refresh feedback templates
New Objective...	`nabsConfidence.newObjective`	Create and edit an objective
Open Objective	`nabsConfidence.openObjective`	Open an objective
Edit Objective...	`nabsConfidence.editObjective`	Create and edit an objective
Objective Assessment...	`nabsConfidence.openObjectiveAssessment`	Assess objectives with Copilot
Archive Retro to Discussion...	`nabsConfidence.archiveRetro`	Check where the archive will go
Open Archived Retro's Discussion	`nabsConfidence.openArchivedRetro`	Find archived retros
Show Objective in Retro	`nabsConfidence.openRetroObjective`	Open an objective
Choose Retro Objectives...	`nabsConfidence.relateObjectives`	Choose which objectives a retro focuses on
Add Objective Evidence...	`nabsConfidence.addObjectiveEvidence`	Add evidence and see automatic measures
Assess Objectives with Copilot	`nabsConfidence.assessObjectives`	Assess objectives with Copilot
Record Objective Verdict...	`nabsConfidence.recordObjectiveVerdict`	Record the team's verdict