Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>KNMNew to Visual Studio Code? Get it now.
KNM

KNM

Ojasa Mirai

|
20 installs
| (0) | Free
KNM project tree, entity detail and Claude Code commands inside VSCode
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

KNM VSCode extension (OjasaMirai.project-conductor)

What it does

KNM turns a project's requirements into working code with Claude Code. The extension is the link between three things: the KNM service (where features, decisions, requirements, work items and tests are stored and approved), the workspace (your repo), and Claude Code (which does the writing).

It does not generate anything itself. It:

  1. Signs you in to KNM and binds the workspace to one KNM project.
  2. Shows the project in the KNM sidebar: Home buttons and a tree of feature > decision > requirement > work item / test, with status and "waiting on " locks for open questions.
  3. Opens an item in a tab with its fields, parent/children links and the next action for its status.
  4. Hands the action to Claude: the button prefills a slash command (e.g. /knm:add-requirement DEC-009) in the Claude Code panel. You press Enter. Nothing runs without you.
  5. Ships the Claude skills and tools as a plugin, so /knm:<skill> commands exist and can talk to KNM.
  6. Applies scaffolding plans (app skeleton from modules) with a headless Claude.

Approvals (requirement, draft review, questionnaire answers) are done by people in KNM; the extension shows their state and enforces the order.

Typical flow

Context docs ──► Import features ──► Decision ──► /knm:add-requirement (draft)
   (docs/project)                                   │ product owner approves, answers questions
                                                    ▼
              /knm:finalize-requirement ◄───────────────┘   writes req.md + mock.md
                        │ owner approves
                        ▼
   /knm:add-workitem → /knm:finalize-workitem → /knm:preview-workitem → /knm:implement-workitem
   /knm:add-test     → /knm:finalize-test     →                      /knm:implement-test

Sidebar

  • Home (top): one Requirements button. It opens the Requirements screen (with a back button to Home): Add Feature(s), Define intent, Import features, Create walkthrough, Create DB design (each prefills a skill in Claude) and Validate context (opens the Context panel, which lists docs/project/context.md and checks it). Add Feature(s) opens a text box; Create saves the text to docs/features/add-features-<stamp>.md and prefills /knm:import-features docs/features/add-features-<stamp>.md, which lists the requirements to create and, separately, those to change (only requirements still at created), and asks which ones in Claude Code.
  • Requirements (tree): the project; the Sync button refreshes it. The badge is the number of open gates (unanswered questions).
  • Status bar: signed out / project name and last sync / sync failed.

Commands

Command Does
KNM: Sign in / Sign out Stores a personal access token in ~/.knm/credentials (mode 600), or removes it
KNM: Select project Binds the workspace to a project (.project-knm/context/config.json)
KNM: Sync Reloads the project from the API
KNM: Open KNM web app Opens the web app (also "Open in web app" per item)
KNM: Install project files (reinstall) Adds or updates the skills, helper tools and settings in the workspace
KNM: Add feature(s) /knm:import-features docs/features/add-features-<stamp>.md: typed text in, requirements to create and to change out
KNM: Define intent /knm:define-intent: the gate for the other skills - creates docs/project/intent.md (purpose, ranked goals, non-goals, success) from the documents, asks you to validate it and to commit it
KNM: Import features /knm:import-features: creates features, decisions and requirements from the context documents
KNM: Create walkthrough /knm:create-walkthrough: clickable mock walkthrough with a gap list
KNM: Create DB design /knm:create-db-design: db_design_tables.csv and db_design.md
Implement DB design (skill, no button yet) /knm:implement-db-design: asks where db_design.md is, writes ORM models and a migration, applies it to the target DB
KNM: Validate context Opens the Context panel and checks docs/project/context.md
KNM: Apply scaffolding plan Applies a saved plan (SCF-xxxx); needs Claude Code and a clean git tree

Skills and tools: shipped inside the extension

Skills, helper tools and the module pack live in plugin/ (a Claude Code plugin named knm) and are not copied into workspaces. Run them as /knm:<skill>, for example /knm:add-requirement DEC-009. On first start the extension asks once to set the Claude Code user setting claudeCode.claudeProcessWrapper to plugin/bin/claude-wrapper.sh, which starts Claude with --plugin-dir; later versions update the path silently. On Windows (a .cmd wrapper cannot be started, EINVAL) the extension instead installs the plugin through the claude program bundled with the Claude Code extension (local marketplace knm-local, plugin/.claude-plugin/marketplace.json). KNM: Register skills with Claude Code asks again.

Each skill pre-allows node ${CLAUDE_PLUGIN_ROOT}/tools/*, so no per-project permission rule is needed.

What bootstrap still writes into the workspace (after a modal; Cancel writes nothing): .project-knm/context/config.json, two .gitignore lines and .claude/settings.json allow rules for git, Read and Edit under docs. Workspaces that hold the old copies (.claude/skills, .project-knm/tools, .project-knm/pack) get one offer to remove them; only files KNM wrote are removed.

Layout of plugin/: .claude-plugin/plugin.json, skills/ (source), tools/ (knm-api.js, knm-context.js built by esbuild.mjs; knm-module.js and walkthrough/), pack/ (built by app/tools/module-pack), bin/claude-wrapper.sh.

Develop

cd app && npm run build -w project-conductor
code --extensionDevelopmentPath=/Users/roopesh/projects/project_knm/app/apps/vscode <workspace folder>

Start the API (npm run dev -w @knm/api, port 8787) and the web app (port 5190), create a personal access token in the web Settings page. Settings: knm.apiBaseUrl (default the deployed function URL), knm.webAppUrl (default https://knm-om.web.app).

Tests: npm test -w project-conductor; against a fresh local API add KNM_TEST_API=http://localhost:8788 (it mutates the seed, use a new file database each run). Package: npm run package -w project-conductor.

Code layout

src/ is plain TS bundled by esbuild into dist/extension.js. Pure modules (no vscode import, unit tested): credentials, config, api, data, treeModel, actions, detailHtml, claudePrompt, webUrl, cache, bootstrap, sync, contextDoc, homeHtml, contextHtml. VSCode-bound: extension, commands, store, tree, detail, home, status, notify, claudeSend, bootstrapUi, contextPanel, contextFs, scaffoldApply, scaffoldApplyUi. files/ is what bootstrap copies into a workspace (only config.json); plugin/ is what Claude loads.

The knm-api helper

node .project-knm/tools/knm-api.js <METHOD> /api/... [--json '<body>' | --file f.json | --stdin] [--query k=v ...], upload --entity-type T --entity-id ID --key K --file f, get <decision|requirement|workitem|test> <id> (looks the id up in your projects and adds projectId), whoami. Built from src/tools/knm-api.ts by npm run build (committed). No dependencies, Node >= 18. stdout is only the JSON data; failures are one line on stderr with the status and API message, exit 1; the token is never printed.

  • Authentication: reads ~/.knm/credentials, falls back to apiBaseUrl in .project-knm/context/config.json, sends Authorization: Bearer. 401/403 or no credentials: "Run KNM: Sign in in VSCode". KNM_CREDENTIALS=<file> overrides the path (tests).
  • Request bodies are written to .knm/tmp/ (gitignored) and passed with --file: Claude Code's shell check rejects braces with quotes in a command. A small --json '{"a":1}' is fine.
  • Allow rules written to .claude/settings.json: Bash(node .project-knm/tools/knm-api.js:*), Read, Edit(/docs/**), Edit(/.project-knm/**), Edit(/.knm/**). Claude Code ignores them until the workspace is trusted; headless runs pass --allowedTools.
  • Skill files and the helper carry knm-managed: v1 version: N.
  • Tests: test/knmApi.test.ts, test/bootstrapSkills.test.ts, test/skillsLint.test.ts (no curl, only the helper, every route exists in the contract).

Scaffolding

KNM: Apply scaffolding plan applies a saved plan with the bundled headless claude and the implement-scaffolding skill (see new_docs/screens/scaffold/design.md section 7). Needs the Claude Code extension and a clean git tree.

Manual checklist (about 15 minutes)

  1. Open a folder with no .project-knm. A modal lists .project-knm/context/config.json and the two .gitignore lines. Cancel it: nothing is written. Run KNM: Install project files (reinstall), press Add files: files appear; run it again: "already in place".
  2. Status bar shows KNM: signed out; the KNM activity bar view shows the welcome buttons.
  3. KNM: Sign in, paste a bad token: readable error. Paste a good token: "signed in", ~/.knm/credentials exists with mode 600.
  4. The project quick pick opens; choose a project. .project-knm/context/config.json has the projectId; status bar shows the project name and "synced hh:mm".
  5. The tree shows feature > decision > requirement > work item and test, ID title, with status text. Gated rows show a lock and "waiting on ". .claude/requirements.json exists and is in .gitignore.
  6. The activity bar badge equals the number of open gates (create questions on a requirement in the web app, press Sync: it goes up).
  7. Click a decision with no requirement: a tab opens with fields, parent link (click it), children list (click one) and Create Requirement (AI) showing /knm:add-requirement <id>.
  8. Press it: the Claude panel opens with the command prefilled and NOT submitted; a notification says to press Enter. (If the panel is empty, paste: the command is on the clipboard.)
  9. Click a gated requirement: Answer questions is disabled with a note. A decision with an open draft shows Review draft, disabled.
  10. Click a finalized, not approved requirement: Approve requirement is offered (a developer token gets "Only the product owner can do this"). Press it as the owner: notification, tree refreshes, tab now shows Create Work Item (AI) and Create Test (AI).
  11. Click a finalized work item: Preview (AI) and Implement (AI) with /knm:preview-workitem <id> and /knm:implement-workitem <id>.
  12. Open in web app opens http://localhost:5190/project/<id>/manage?f=...&r=....
  13. Change something in the web app, press Sync in the tree title: the tree and any open tab update.
  14. Stop the API and press Sync: a readable "Cannot reach the KNM API" notification, status bar shows "sync failed".
  15. KNM: Sign out: credentials file is gone, tree shows the sign-in welcome view, status bar says signed out.
  16. Skills: in a workspace that still has the old skills, a warning offers "Back up and install"; accept: SKILL.md.bak files appear and the new skills are in place. .claude/settings.json has the allow rules and other keys are intact.
  17. In the Claude panel run /knm:add-requirement DEC-009 (workspace trusted): no permission prompts; it ends with "Draft saved. Review and approve it in KNM ..." and the requirement is NOT created. After approving the draft and answering its questions in KNM, /knm:finalize-requirement <REQ-id> writes req.md and mock.md and the status becomes finalized.
  18. Sign out and run any skill: the answer says to run "KNM: Sign in".
  19. Home view: Requirements opens the Requirements screen (and back); there Define intent, Import features, Create walkthrough, Create DB design prefill their command in Claude and Validate context opens the Context panel.
  20. Add Feature(s): Create is disabled until text is typed; Create prefills /knm:import-features docs/features/add-features-<stamp>.md and the file holds the text. In Claude, the skill lists requirements to create and to change, asks which, and leaves finalized/approved ones alone.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft