fix(12): revise plans based on checker feedback

- Plan 12-01: Reframe must_haves.truths to be user-observable
  (was implementation-focused, now user-outcome focused)
- Plan 12-02: Add PROD-05 (README quick start) and PROD-06
  (docs/TOOLS.md) verification to Task 3, add artifacts/key_links
- Plan 12-03: Fix depends_on format from ["12-01", "12-02"]
  to ["01", "02"] for consistency

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: kunwarVivek

.planning/phases/12-production-release/12-01-PLAN.md

@@ -12,9 +12,9 @@ autonomous: true
 
 must_haves:
   truths:
-    - "npm test reports 0 failing tests"
-    - "All E2E tests either pass or are skipped with documented justification"
-    - "Test suite completes successfully in CI-like environment"
+    - "User can install package and run tests without failures blocking release"
+    - "Production build is verified stable by passing test suite"
+    - "Package is ready for distribution with documented test coverage"
   artifacts:
     - path: "src/__tests__/e2e/stdio-transport.e2e.ts"
       provides: "Fixed stdio transport E2E tests"

.planning/phases/12-production-release/12-02-PLAN.md

@@ -15,13 +15,21 @@ must_haves:
     - "User can configure the MCP server using documented environment variables"
     - "User can troubleshoot common issues using the troubleshooting guide"
     - "README points to detailed configuration and troubleshooting docs"
+    - "README has working quick start instructions (PROD-05)"
+    - "Tool reference documentation is complete with 119 tools (PROD-06)"
   artifacts:
     - path: "docs/CONFIGURATION.md"
       provides: "Complete configuration reference"
       min_lines: 100
     - path: "docs/TROUBLESHOOTING.md"
       provides: "Troubleshooting guide for common issues"
       min_lines: 80
+    - path: "README.md"
+      provides: "Quick start instructions"
+      contains: "Quick Start"
+    - path: "docs/TOOLS.md"
+      provides: "Tool reference documentation"
+      min_lines: 1800
   key_links:
     - from: "README.md"
       to: "docs/CONFIGURATION.md"
@@ -31,14 +39,18 @@ must_haves:
       to: "docs/TROUBLESHOOTING.md"
       via: "markdown link"
       pattern: "\\[.*\\]\\(docs/TROUBLESHOOTING\\.md\\)"
+    - from: "README.md"
+      to: "docs/TOOLS.md"
+      via: "markdown link"
+      pattern: "\\[.*\\]\\(docs/TOOLS\\.md\\)"
 ---
 
 <objective>
-Create comprehensive configuration and troubleshooting documentation.
+Create comprehensive configuration and troubleshooting documentation, and verify README quick start and tool reference are complete.
 
-Purpose: PROD-07 and PROD-08 require configuration and troubleshooting guides. These are essential for npm package users to successfully set up and use the MCP server.
+Purpose: PROD-05, PROD-06, PROD-07, PROD-08 require complete user documentation. These are essential for npm package users to successfully set up and use the MCP server.
 
-Output: docs/CONFIGURATION.md (all config options), docs/TROUBLESHOOTING.md (common issues/solutions), updated README links.
+Output: docs/CONFIGURATION.md (all config options), docs/TROUBLESHOOTING.md (common issues/solutions), verified README quick start, verified docs/TOOLS.md completeness.
 </objective>
 
 <execution_context>
@@ -173,10 +185,36 @@ Include copy-pasteable solutions for each issue.
 </task>
 
 <task type="auto">
-  <name>Task 3: Update README with documentation links</name>
-  <files>README.md</files>
+  <name>Task 3: Verify README quick start and tool reference, update documentation links</name>
+  <files>README.md, docs/TOOLS.md</files>
   <action>
-Update README.md to add links to the new documentation:
+**VERIFY README QUICK START (PROD-05):**
+
+1. Check README.md has a "Quick Start" section with:
+   - Installation command (`npx mcp-github-project-manager` or `npm install -g`)
+   - Minimum required environment variables (GITHUB_TOKEN, GITHUB_OWNER, GITHUB_REPO)
+   - Basic usage example
+   - Link to detailed configuration
+
+2. If Quick Start section is missing or incomplete:
+   - Add/update Quick Start section near the top of README
+   - Include 3-5 step getting started guide
+   - Keep it concise - link to detailed docs for more info
+
+**VERIFY TOOL REFERENCE (PROD-06):**
+
+1. Check docs/TOOLS.md exists and contains documentation for all 119 tools:
+   ```bash
+   grep -c "^### \`" docs/TOOLS.md  # Should show ~119 tool headers
+   ```
+
+2. Verify tool categories are documented:
+   - Project Management, Issue Management, Sprint Planning
+   - AI-powered tools, Label Management, etc.
+
+3. If TOOLS.md is missing or incomplete, flag for creation (should already exist from Phase 11)
+
+**UPDATE README DOCUMENTATION LINKS:**
 
 1. Add a "Documentation" section after "Table of Contents" (or update existing one):
    ```markdown
@@ -200,11 +238,14 @@ Update README.md to add links to the new documentation:
 Keep changes minimal - only add/update links, don't restructure the README.
   </action>
   <verify>
-1. README.md contains link to docs/CONFIGURATION.md
-2. README.md contains link to docs/TROUBLESHOOTING.md
-3. Links are valid markdown format
+1. README.md contains "Quick Start" section with installation and basic usage
+2. README.md contains link to docs/CONFIGURATION.md
+3. README.md contains link to docs/TROUBLESHOOTING.md
+4. README.md contains link to docs/TOOLS.md
+5. docs/TOOLS.md exists with 119 tools documented (grep count ~119)
+6. Links are valid markdown format
   </verify>
-  <done>README.md updated with links to new documentation</done>
+  <done>README.md verified with quick start, docs/TOOLS.md verified complete (119 tools), all documentation links updated</done>
 </task>
 
 </tasks>
@@ -214,22 +255,33 @@ Keep changes minimal - only add/update links, don't restructure the README.
 # Verify files exist
 test -f docs/CONFIGURATION.md && echo "CONFIGURATION.md exists"
 test -f docs/TROUBLESHOOTING.md && echo "TROUBLESHOOTING.md exists"
+test -f docs/TOOLS.md && echo "TOOLS.md exists"
 
 # Verify minimum line counts
 wc -l docs/CONFIGURATION.md  # Should be 100+
 wc -l docs/TROUBLESHOOTING.md  # Should be 80+
+wc -l docs/TOOLS.md  # Should be 1800+
+
+# Verify README has Quick Start
+grep -i "quick start" README.md
 
 # Verify README links
 grep -E "docs/CONFIGURATION\.md" README.md
 grep -E "docs/TROUBLESHOOTING\.md" README.md
+grep -E "docs/TOOLS\.md" README.md
+
+# Verify tool count
+grep -c "^### \`" docs/TOOLS.md  # Should be ~119
 ```
 </verification>
 
 <success_criteria>
 1. docs/CONFIGURATION.md exists with all config options documented
 2. docs/TROUBLESHOOTING.md exists with common issues and solutions
-3. README.md links to both new documents
-4. PROD-07 and PROD-08 requirements met
+3. README.md has Quick Start section (PROD-05)
+4. docs/TOOLS.md has 119 tools documented (PROD-06)
+5. README.md links to all documentation files
+6. PROD-05, PROD-06, PROD-07, PROD-08 requirements met
 </success_criteria>
 
 <output>

.planning/phases/12-production-release/12-03-PLAN.md

@@ -3,7 +3,7 @@ phase: 12-production-release
 plan: 03
 type: execute
 wave: 2
-depends_on: ["12-01", "12-02"]
+depends_on: ["01", "02"]
 files_modified:
   - CHANGELOG.md
   - package.json