Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>Kiro Spec ProgressNew to Visual Studio Code? Get it now.
Kiro Spec Progress

Kiro Spec Progress

Digital Defiance

| (0) | Free
Progress bars for your Kiro specs: shows % complete per spec by counting the task checkboxes in .kiro/specs/*/tasks.md.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Kiro Spec Progress

A tiny VS Code / Kiro extension that reads .kiro/specs/*/tasks.md, counts checkboxes, and shows a progress bar per spec in its own sidebar tab (plus an overall % in the status bar).

  • - [x] done, - [ ] todo, - [-] / - [~] in progress (counted as not done)
  • - [ ]* ... optional tasks (toggle with kiroSpecProgress.includeOptional)
  • Sub-tasks are counted too; set kiroSpecProgress.topLevelOnly to count only top-level tasks
  • Checkboxes inside ``` code fences are ignored
  • Click a spec to open its tasks.md. Updates live as you edit (even before saving).

Install

kiro --install-extension kiro-spec-progress-0.1.0.vsix   # or: code --install-extension ...

Or: Extensions view → ... → Install from VSIX...

Hack on it

  • src/parse.js — the counting logic (no VS Code deps). npm test runs test/parse.test.js.
  • src/extension.js — scanning, file watching, the webview HTML/CSS.
  • F5 launches an Extension Development Host on test/fixtures (sample specs).
  • Rebuild the .vsix: npm run build (see below).

Build & publish

One-time setup:

npm install                                   # installs vsce + ovsx locally
npx vsce login digitaldefiance                # Azure DevOps PAT (Marketplace > Manage scope)
export OVSX_PAT=...                           # token from open-vsx.org (Kiro installs from Open VSX)
npx ovsx create-namespace digitaldefiance     # first time only

Scripts:

Command What it does
npm run build Runs the tests, then packages dist/kiro-spec-progress-<version>.vsix
npm run publish Build, then publish that same .vsix to the VS Code Marketplace and Open VSX
npm run publish:vsce / publish:ovsx Publish an already-built .vsix to just one store
npm run release:patch / release:minor Bump the version (commit + tag via npm version), then publish

package.json has "private": true so a stray npm publish can't push this to the npm registry.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft