- Version: 2.0
Updates project context documents with version control, consistency validation, and impact analysis across related files.
/plugin marketplace add ninthspace/claude-code-marketplace/plugin install sdd@ninthspace-marketplacePurpose: Update technical stack, development process, coding standards, or project glossary documents while maintaining consistency across all project context files.
Syntax: /sdd:project-context-update [document_type]
| Parameter | Type | Required | Default | Description | Validation |
|---|---|---|---|---|---|
| document_type | string | No | prompted | Which document to update | One of: technical-stack, development-process, coding-standards, project-glossary, project-brief |
/docs/project-context//docs/project-context/ directory exists/sdd:project-init first/docs/project-context/technical-stack.md - Technology choices/docs/project-context/coding-standards.md - Quality rules/docs/project-context/development-process.md - Workflow definitions/docs/project-context/project-glossary.md - Domain vocabulary/docs/project-context/project-brief.md - Project overviewWhich document would you like to update?
1. technical-stack - Frameworks, languages, tools
2. development-process - Stage definitions, workflows
3. coding-standards - Naming, patterns, quality requirements
4. project-glossary - Domain terms, project vocabulary
5. project-brief - Project overview and goals
Enter number or name:
/docs/project-context/[target_document].mdASK user what changes to make:
GATHER specific details:
ASK for version numbers and documentation links (if technical change)
ANALYZE impact on other context documents:
IF updating technical-stack:
IF updating coding-standards:
IF updating development-process:
IF updating project-glossary:
REPORT identified impacts to user:
Impact Analysis:
━━━━━━━━━━━━━━━━
Primary Change: technical-stack.md
Affected Documents:
- coding-standards.md: Test command references need update
- development-process.md: QA stage testing strategy needs alignment
Affected Stories:
- 2 stories in /development may need test updates
- 1 story in /review may need coding standard adjustments
CREATE backup before modifications:
/docs/project-context/versions/[document]-backup-[timestamp].mdAPPLY changes to target document:
SAVE updated document to original location
VALIDATE consistency across project-context:
DETECT inconsistencies or conflicts:
REPORT validation results to user
IF other documents affected:
IF user declines cascading updates:
IDENTIFY stories affected by context changes:
/docs/stories/development/ for impacted stories/docs/stories/review/ for stories needing review updates/docs/stories/qa/ stories requiring test updatesSUGGEST actions for affected stories:
/sdd:story-review for stories with new standards/sdd:story-qa for stories with new test requirementsDISPLAY update summary:
✅ Context Document Updated
═══════════════════════════════════
Document: technical-stack.md
Backup: /docs/project-context/versions/technical-stack-backup-20251001-104500.md
Changes Applied:
- Added: Playwright for E2E testing
- Updated: Node.js version 18 → 20
- Removed: Deprecated library XYZ
Cascading Updates:
- coding-standards.md: Updated test naming conventions
- development-process.md: Added Playwright to QA stage
Affected Stories: 2 in development
Recommended Actions:
1. Review STORY-XXX-005 test setup
2. Update STORY-XXX-007 with new standards
PROVIDE next steps:
/docs/project-context/[document].md - Modified context document/docs/project-context/versions/[document]-backup-[timestamp].md - Original versionINPUT:
/sdd:project-context-update technical-stack
INTERACTION:
→ Shows current technical-stack.md content
→ Asks: "What would you like to update?"
→ User: "Add Playwright for E2E testing"
→ Asks: "Version number?" → "1.40"
→ Asks: "Documentation link?" → "https://playwright.dev"
IMPACT ANALYSIS:
Analyzing impact...
- coding-standards.md: Test naming conventions need update
- development-process.md: QA stage needs Playwright integration
- 2 stories in /development may need test updates
OUTPUT:
✅ Context Document Updated
═══════════════════════════════════
Document: technical-stack.md
Backup: /docs/project-context/versions/technical-stack-backup-20251001-104500.md
Changes Applied:
- Added: Playwright 1.40 for E2E testing
- Updated: Browser/E2E testing section
Cascading Updates Available:
1. coding-standards.md - Add Playwright test patterns
2. development-process.md - Update QA stage with Playwright
Would you like to apply cascading updates now? [y/n]
INPUT:
/sdd:project-context-update technical-stack
INTERACTION:
→ Asks: "What would you like to update?"
→ User: "Migrate from Jest to Vitest"
IMPACT ANALYSIS:
⚠️ Major Change Detected: Test Framework Migration
Affected Documents:
- technical-stack.md: Unit testing framework
- coding-standards.md: Test file conventions, imports
- development-process.md: Test commands in all stages
- project-glossary.md: Testing terminology
Affected Stories:
- 5 stories in /development with existing tests
- 2 stories in /review with test coverage
- 3 stories in /completed may need test migration
OUTPUT:
✅ Context Document Updated
═══════════════════════════════════
Document: technical-stack.md
Backup: /docs/project-context/versions/technical-stack-backup-20251001-104530.md
Changes Applied:
- Removed: Jest (deprecated)
- Added: Vitest 1.0 (new unit testing framework)
- Updated: Test runner commands (npm test → vitest)
Cascading Updates Required:
1. coding-standards.md: Test import statements (expect from 'vitest')
2. development-process.md: Test commands in all stages
3. project-glossary.md: Update testing terminology
⚠️ IMPORTANT: Existing Stories Need Updates
- 5 stories in /development require test migration
- Consider creating migration guide story
Recommended Actions:
1. Update all context documents (run /sdd:project-context-update)
2. Create STORY-MIGRATION: Jest to Vitest migration guide
3. Re-run tests for all in-progress stories
4. Update test templates in /docs/stories/templates/
INPUT:
/sdd:project-context-update coding-standards
INTERACTION:
→ Shows current coding-standards.md
→ Asks: "What would you like to update?"
→ User: "Change line length from 80 to 120 characters"
IMPACT ANALYSIS:
Analyzing impact...
- Technical stack: No changes needed
- Development process: No changes needed
- Existing code: May need reformatting
- Stories: 3 in /review may need re-review
OUTPUT:
✅ Context Document Updated
═══════════════════════════════════
Document: coding-standards.md
Backup: /docs/project-context/versions/coding-standards-backup-20251001-104600.md
Changes Applied:
- Updated: Line length limit 80 → 120 characters
- Updated: Prettier configuration reference
No cascading updates required.
⚠️ Code Formatting Impact:
- Existing code may need reformatting
- Run: npm run format (or equivalent)
- Consider: Re-review 3 stories in /review with new standard
Recommended Actions:
1. Run formatter across codebase
2. Re-review STORY-XXX-003, STORY-XXX-006, STORY-XXX-009
3. Update editor/IDE settings to 120 char limit
INPUT:
/sdd:project-context-update
OUTPUT:
⚠️ PROJECT CONTEXT NOT FOUND
The /docs/project-context/ directory does not exist.
To set up the story-driven development system, run:
→ /sdd:project-init
This will create:
- Project context directory
- All context documents
- Document templates
/sdd:project-init/sdd:project-init with clear instructions/sdd:project-init - Initialize project structure if missing/sdd:project-brief - Update high-level project documentation/sdd:story-review - Re-review stories with new standards/sdd:story-qa - Re-test stories with new requirements/sdd:project-status - View current project state