Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Project ConductorNew to Visual Studio Code? Get it now.
Project Conductor

Project Conductor

Ojasa Mirai

|
2 installs
| (0) | Free
Orchestrate your complete project lifecycle—from requirements to deployment.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Project Conductor

Orchestrate your complete project lifecycle—from requirements to deployment.

Project Conductor is a VS Code extension that helps you manage and validate projects at every stage: requirements definition, decision tracking, work item planning, test management, and deployment orchestration. Keep everything organized in your editor without switching contexts.

Features

  • 📋 Requirements Management — Define, organize, and track requirements hierarchically
  • 🎯 Decision Tracking — Document decisions tied to requirements with approval workflows
  • ✅ Work Items & Tests — Plan work items and tests directly from decisions
  • 📝 In-Editor Questionnaires — Answer validation questionnaires without leaving VS Code
  • 🔄 Real-Time Sync — Sync your data with a backend database (optional)
  • 🌙 Dark Mode Support — Full dark/light theme support for comfortable development
  • 📁 Local-First — All data stored locally in requirements.json with optional cloud sync

Installation

  1. Open VS Code
  2. Go to Extensions (Ctrl+Shift+X / Cmd+Shift+X)
  3. Search for "Project Conductor"
  4. Click Install

Or install directly from the VS Code Marketplace

Quick Start

1. Initialize Your Project

When you first open the extension, it creates a requirements.json file in your workspace with the following structure:

{
  "project": {
    "id": "PROJ-001",
    "name": "My Project",
    "description": "Project description",
    "updated_at": "2026-08-18T...",
    "_local_changes": false
  },
  "requirements": [],
  "decisions": [],
  "changeRequests": [],
  "workItems": [],
  "tests": []
}

2. Create Requirements

  1. Open the Project Conductor sidebar (Activity Bar icon)
  2. Navigate to the project
  3. Click Add Requirement to define what needs to be built
  4. Link requirements to decisions for traceability

3. Make Decisions

  1. Attach decisions to requirements
  2. Track approval status and metadata
  3. Link work items to decisions for implementation tracking

4. Answer Questionnaires

Use the Answer Questionnaire feature to validate documents and gather feedback:

  1. Click the checklist icon (checklist) in the Project Conductor sidebar, OR

  2. Right-click a .json questionnaire file in the Explorer and select Answer Questionnaire, OR

  3. Press Ctrl+Shift+P (Cmd+Shift+P) and search Answer Questionnaire

  4. Fill in the form directly in the editor

  5. Submit to save answers back to the same file

Example questionnaire format:

{
  "title": "Document Validation",
  "description": "Review and validate the document",
  "status": "pending",
  "questions": [
    {
      "id": "q1",
      "type": "single_choice",
      "text": "Does the document match requirements?",
      "options": ["Yes", "No", "Partial"],
      "required": true,
      "answer": null
    },
    {
      "id": "q2",
      "type": "yes_no",
      "text": "Is the signature valid?",
      "required": true,
      "answer": null
    },
    {
      "id": "q3",
      "type": "multi_choice",
      "text": "Which sections were reviewed?",
      "options": ["Section A", "Section B", "Section C"],
      "required": false,
      "answer": null
    },
    {
      "id": "q4",
      "type": "text",
      "text": "Any corrections needed?",
      "required": false,
      "answer": null
    },
    {
      "id": "q5",
      "type": "long_text",
      "text": "Overall comments",
      "required": false,
      "answer": null
    }
  ]
}

After you submit, the questionnaire is updated with:

  • status: "completed"
  • completedAt: "2026-08-18T15:42:03Z"
  • All answers populated in the answer field for each question

5. Plan Work Items & Tests

  1. From a decision, create work items for implementation
  2. Add tests to verify work items are complete
  3. Track status through the entire development cycle

Question Types

The questionnaire feature supports 5 question types:

Type Answer Type Use Case
single_choice string Multiple options, one answer
multi_choice string[] Multiple options, multiple answers
yes_no "Yes" | "No" Binary questions
text string Short single-line responses
long_text string Multi-line responses, notes

Settings & Configuration

All data is stored in requirements.json at your workspace root. You can edit this file directly or through the UI.

Optional: Configure backend sync in the extension settings for cloud storage and team collaboration.

Keyboard Shortcuts

  • Ctrl+Shift+P (Cmd+Shift+P) — Command palette: search "Answer Questionnaire"
  • Ctrl+K Ctrl+O — Open Project Conductor sidebar

Tips & Tricks

  • Offline-first — Everything works without internet. Sync is optional.
  • Version control — Commit requirements.json to git for full project history.
  • Share questionnaires — Copy .json questionnaire files to share with teammates.
  • Batch operations — Edit requirements.json directly for bulk changes.

Support & Feedback

  • Report bugs: GitHub Issues
  • Feature requests: Create an issue with the enhancement label
  • Questions: Use GitHub Discussions

License

MIT License — See LICENSE file for details

Changelog

0.1.1 (2026-08-18)

  • ✨ Initial release
  • 📋 Requirements, decisions, work items, and tests management
  • 📝 In-extension questionnaire answering
  • 🌙 Dark mode support
  • 🔄 Local-first architecture with optional backend sync
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft