diff --git a/packages/content-ops/src/markdown/link-processor.test.ts b/packages/content-ops/src/markdown/link-processor.test.ts index dffa0cec..1d720b55 100644 --- a/packages/content-ops/src/markdown/link-processor.test.ts +++ b/packages/content-ops/src/markdown/link-processor.test.ts @@ -744,6 +744,89 @@ it('should preserve encoded query and anchor characters when normalizing', async expect(replacements[0].kind).toBe('normalizedRel') }) +describe('generateNormalizationReplacements - no full normalization', () => { + it('should NOT convert cross-folder relative paths to docsFolders-based paths', async function () { + // Scenario: a skill file in .skills/ references a file in .pair/ using a correct relative path. + // The normalizer should NOT rewrite it to a .pair/-prefix path because that breaks + // navigability in IDEs, GitHub, and the link rewriter during distribution. + const fs = new InMemoryFileSystemService( + { + '/dataset/.pair/adoption/tech/way-of-working.md': '# Way of Working', + '/dataset/.skills/capability/verify-quality/SKILL.md': + 'See [wow](../../../.pair/adoption/tech/way-of-working.md).', + }, + '/', + '/', + ) + + const links: ParsedLink[] = [ + { + href: '../../../.pair/adoption/tech/way-of-working.md', + text: 'wow', + line: 1, + start: 4, + end: 60, + }, + ] + + const config: LinkProcessingConfig = { + docsFolders: ['.pair', '.skills', '.github'], + datasetRoot: '/dataset', + exclusionList: [], + } + + const replacements = await LinkProcessor.generateNormalizationReplacements( + links, + '/dataset/.skills/capability/verify-quality/SKILL.md', + config, + fs, + ) + + // The relative path is already correct and navigable — no replacement should be generated + expect(replacements).toHaveLength(0) + }) + + it('should still normalize redundant relative paths within the same folder', async function () { + // Scenario: a file references a sibling with ../same-dir/ prefix — can be simplified + const fs = new InMemoryFileSystemService( + { + '/dataset/.pair/knowledge/how-to/guide.md': '# Guide', + '/dataset/.pair/knowledge/how-to/other.md': 'See [guide](../how-to/guide.md).', + }, + '/', + '/', + ) + + const links: ParsedLink[] = [ + { + href: '../how-to/guide.md', + text: 'guide', + line: 1, + start: 4, + end: 30, + }, + ] + + const config: LinkProcessingConfig = { + docsFolders: ['.pair', '.skills'], + datasetRoot: '/dataset', + exclusionList: [], + } + + const replacements = await LinkProcessor.generateNormalizationReplacements( + links, + '/dataset/.pair/knowledge/how-to/other.md', + config, + fs, + ) + + // ../how-to/guide.md → guide.md (same directory, simpler relative path) + expect(replacements).toHaveLength(1) + expect(replacements[0].newHref).toBe('guide.md') + expect(replacements[0].kind).toBe('normalizedRel') + }) +}) + describe('LinkProcessor - detectLinkStyle', () => { const cwd = '/test' diff --git a/packages/content-ops/src/markdown/link-processor.ts b/packages/content-ops/src/markdown/link-processor.ts index 25e0e69a..11a7ce63 100644 --- a/packages/content-ops/src/markdown/link-processor.ts +++ b/packages/content-ops/src/markdown/link-processor.ts @@ -235,19 +235,6 @@ export class LinkProcessor { fileService: FileSystemService query: string anchor: string - }) { - return this.handleFullNormalization(params) - } - - private static async handleFullNormalization(params: { - replacements: Replacement[] - lnk: ParsedLink - linkPath: string - absTarget: string - config: LinkProcessingConfig - fileService: FileSystemService - query: string - anchor: string }) { const { replacements, lnk, linkPath, absTarget, config, fileService, anchor } = params const { query } = params @@ -269,19 +256,12 @@ export class LinkProcessor { normalized, relToDocs, }) - return } - // handle multi-file path normalization - await this.tryPushMultiFileNormalization({ - replacements, - lnk, - linkPath, - absTarget, - config, - fileService, - normalized, - }) + // Multi-file path normalization (converting relative paths to docsFolders-based + // paths like .pair/adoption/tech/...) is intentionally disabled. These non-standard + // paths are not navigable in IDEs/GitHub and break the link rewriter during skill + // distribution. Relative paths (e.g., ../../../.pair/...) are correct and work everywhere. } private static async tryPushSingleFileNormalization(params: { @@ -308,30 +288,6 @@ export class LinkProcessor { } } - private static async tryPushMultiFileNormalization(params: { - replacements: Replacement[] - lnk: ParsedLink - linkPath: string - absTarget: string - config: LinkProcessingConfig - fileService: FileSystemService - normalized: string - }) { - const { replacements, lnk, linkPath, absTarget, config, fileService, normalized } = params - const topFolder = normalized.split('/')[0] ?? '' - if (!config.docsFolders.includes(topFolder)) return - if (!(await fileService.exists(absTarget))) return - if (linkPath !== normalized) { - this.pushNormalizedReplacement({ - replacements, - lnk, - oldHref: linkPath, - newHref: normalized, - kind: 'normalizedFull', - }) - } - } - private static isSkippableLink(url: string, config: LinkProcessingConfig) { return ( !url || diff --git a/packages/content-ops/src/markdown/replacement-generator.test.ts b/packages/content-ops/src/markdown/replacement-generator.test.ts index 07ba69a3..bfea3f77 100644 --- a/packages/content-ops/src/markdown/replacement-generator.test.ts +++ b/packages/content-ops/src/markdown/replacement-generator.test.ts @@ -50,9 +50,10 @@ describe('generateNormalizationReplacements - basics', () => { fs, ) - expect(replacements).toHaveLength(2) - expect(replacements[0].newHref).toBe('api/ref.md') - expect(replacements[1].newHref).toBe('other.md') + // Only normalizedRel (./other.md → other.md) should be generated. + // ../api/ref.md is already a correct relative path — no full normalization. + expect(replacements).toHaveLength(1) + expect(replacements[0].newHref).toBe('other.md') }) }) diff --git a/packages/knowledge-hub/dataset/.github/agents/product-engineer.agent.md b/packages/knowledge-hub/dataset/.github/agents/product-engineer.agent.md index 4add4dd2..02c2873e 100644 --- a/packages/knowledge-hub/dataset/.github/agents/product-engineer.agent.md +++ b/packages/knowledge-hub/dataset/.github/agents/product-engineer.agent.md @@ -12,13 +12,13 @@ You are a Product Engineer working in an AI-assisted development process followi Based on the how-to guides, you handle these development and implementation activities: ### ⚙️ **Task & Implementation Management (Your Primary Domain)** -- **Create Tasks** → [09-how-to-create-tasks.md](.pair/knowledge/how-to/09-how-to-create-tasks.md) +- **Create Tasks** → [09-how-to-create-tasks.md](../../.pair/knowledge/how-to/09-how-to-create-tasks.md) - *Role: Product Engineer (Story Implementation Planning)* -- **Implement Tasks** → [10-how-to-implement-a-task.md](.pair/knowledge/how-to/10-how-to-implement-a-task.md) +- **Implement Tasks** → [10-how-to-implement-a-task.md](../../.pair/knowledge/how-to/10-how-to-implement-a-task.md) - *Role: Product Software Engineer (Implementation)* ### 📝 **Story Collaboration** -- **Refine User Stories** → [08-how-to-refine-a-user-story.md](.pair/knowledge/how-to/08-how-to-refine-a-user-story.md) +- **Refine User Stories** → [08-how-to-refine-a-user-story.md](../../.pair/knowledge/how-to/08-how-to-refine-a-user-story.md) - *Role: Product Engineer (Technical Refinement)* - *Note: Collaborate with Product Manager on technical aspects* diff --git a/packages/knowledge-hub/dataset/.github/agents/product-manager.agent.md b/packages/knowledge-hub/dataset/.github/agents/product-manager.agent.md index a861c38e..8d140450 100644 --- a/packages/knowledge-hub/dataset/.github/agents/product-manager.agent.md +++ b/packages/knowledge-hub/dataset/.github/agents/product-manager.agent.md @@ -12,19 +12,19 @@ You are a Product Manager working in an AI-assisted development process followin Based on the how-to guides, you handle these strategic and planning activities: ### 🎯 **Strategic Planning (Your Primary Domain)** -- **Create PRD** → [01-how-to-create-PRD.md](.pair/knowledge/how-to/01-how-to-create-PRD.md) +- **Create PRD** → [01-how-to-create-PRD.md](../../.pair/knowledge/how-to/01-how-to-create-PRD.md) - *Role: Product Manager (PRD Creation)* -- **Create and Prioritize Initiatives** → [03-how-to-create-and-prioritize-initiatives.md](.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md) +- **Create and Prioritize Initiatives** → [03-how-to-create-and-prioritize-initiatives.md](../../.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md) - *Role: Product Owner/Manager (Strategic Decomposition)* -- **Define Subdomains** → [04-how-to-define-subdomains.md](.pair/knowledge/how-to/04-how-to-define-subdomains.md) +- **Define Subdomains** → [04-how-to-define-subdomains.md](../../.pair/knowledge/how-to/04-how-to-define-subdomains.md) - *Role: Product Manager (Domain Modeling)* ### 📋 **Epic & Story Management** -- **Breakdown Epics** → [06-how-to-breakdown-epics.md](.pair/knowledge/how-to/06-how-to-breakdown-epics.md) +- **Breakdown Epics** → [06-how-to-breakdown-epics.md](../../.pair/knowledge/how-to/06-how-to-breakdown-epics.md) - *Role: Product Owner/Manager (Strategic Decomposition)* -- **Breakdown User Stories** → [07-how-to-breakdown-user-stories.md](.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md) +- **Breakdown User Stories** → [07-how-to-breakdown-user-stories.md](../../.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md) - *Role: Product Manager (Story Creation)* -- **Refine User Stories** → [08-how-to-refine-a-user-story.md](.pair/knowledge/how-to/08-how-to-refine-a-user-story.md) +- **Refine User Stories** → [08-how-to-refine-a-user-story.md](../../.pair/knowledge/how-to/08-how-to-refine-a-user-story.md) - *Role: Product Manager (Story Refinement)* ## Process Guidelines diff --git a/packages/knowledge-hub/dataset/.github/prompts/bounded-contexts.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/bounded-contexts.prompt.md index 67816572..a204e7c6 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/bounded-contexts.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/bounded-contexts.prompt.md @@ -10,7 +10,7 @@ You are helping define bounded contexts that translate business subdomains into ## Process -**Read and follow** the complete process from [how-to-define-bounded-contexts.md](.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md). +**Read and follow** the complete process from [how-to-define-bounded-contexts.md](../../.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md). **Execute the process exactly as documented**, including: - All phases and checkpoints diff --git a/packages/knowledge-hub/dataset/.github/prompts/breakdown-epics.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/breakdown-epics.prompt.md index db51ea6a..e8cabccc 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/breakdown-epics.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/breakdown-epics.prompt.md @@ -12,7 +12,7 @@ If an initiative ID is provided (e.g., `/breakdown-epics: initiative_id=INIT-123 ## Process -**Read and follow** the complete process from [how-to-breakdown-epics.md](.pair/knowledge/how-to/06-how-to-breakdown-epics.md). +**Read and follow** the complete process from [how-to-breakdown-epics.md](../../.pair/knowledge/how-to/06-how-to-breakdown-epics.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/breakdown-stories.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/breakdown-stories.prompt.md index 0366179f..f1fc7006 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/breakdown-stories.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/breakdown-stories.prompt.md @@ -12,7 +12,7 @@ If an epic ID is provided (e.g., `/breakdown-stories: epic_id=EPIC-123`), focus ## Process -**Read and follow** the complete process from [how-to-breakdown-user-stories.md](.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md). +**Read and follow** the complete process from [how-to-breakdown-user-stories.md](../../.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/code-review.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/code-review.prompt.md index 6ff67136..63eecc7d 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/code-review.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/code-review.prompt.md @@ -13,7 +13,7 @@ If a story ID is provided (e.g., `/code-review: story_id=STORY-456`), search for ## Process -**Read and follow** the complete process from [how-to-code-review.md](.pair/knowledge/how-to/11-how-to-code-review.md). +**Read and follow** the complete process from [how-to-code-review.md](../../.pair/knowledge/how-to/11-how-to-code-review.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/complete-bootstrap-checklist.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/complete-bootstrap-checklist.prompt.md index cfa71067..6a8374b7 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/complete-bootstrap-checklist.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/complete-bootstrap-checklist.prompt.md @@ -10,7 +10,7 @@ You are helping complete the bootstrap checklist to establish a solid project fo ## Process -**Read and follow** the complete process from [how-to-complete-bootstrap-checklist.md](.pair/knowledge/how-to/02-how-to-complete-bootstrap-checklist.md). +**Read and follow** the complete process from [how-to-complete-bootstrap-checklist.md](../../.pair/knowledge/how-to/02-how-to-complete-bootstrap-checklist.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/create-prd.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/create-prd.prompt.md index ebd1a3d0..3b46b56e 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/create-prd.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/create-prd.prompt.md @@ -10,7 +10,7 @@ You are helping create a Product Requirements Document (PRD) for a product or fe ## Process -**Read and follow** the complete process from [how-to-create-PRD.md](.pair/knowledge/how-to/01-how-to-create-PRD.md). +**Read and follow** the complete process from [how-to-create-PRD.md](../../.pair/knowledge/how-to/01-how-to-create-PRD.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/create-prioritize-initiatives.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/create-prioritize-initiatives.prompt.md index 5ca49408..db4bb138 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/create-prioritize-initiatives.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/create-prioritize-initiatives.prompt.md @@ -10,7 +10,7 @@ You are helping create and prioritize strategic initiatives that translate PRD r ## Process -**Read and follow** the complete process from [how-to-create-and-prioritize-initiatives.md](.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md). +**Read and follow** the complete process from [how-to-create-and-prioritize-initiatives.md](../../.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/create-tasks.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/create-tasks.prompt.md index 5a666f10..009d5a91 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/create-tasks.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/create-tasks.prompt.md @@ -12,7 +12,7 @@ If a story ID is provided (e.g., `/create-tasks: story_id=STORY-123`), focus on ## Process -**Read and follow** the complete process from [how-to-create-tasks.md](.pair/knowledge/how-to/09-how-to-create-tasks.md). +**Read and follow** the complete process from [how-to-create-tasks.md](../../.pair/knowledge/how-to/09-how-to-create-tasks.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/define-bounded-contexts.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/define-bounded-contexts.prompt.md index 03cf40a1..bdac0f2d 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/define-bounded-contexts.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/define-bounded-contexts.prompt.md @@ -10,7 +10,7 @@ You are helping define bounded contexts that translate business subdomains into ## Process -**Read and follow** the complete process from [how-to-define-bounded-contexts.md](.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md). +**Read and follow** the complete process from [how-to-define-bounded-contexts.md](../../.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/define-subdomains.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/define-subdomains.prompt.md index 551f81a5..aa296e8f 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/define-subdomains.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/define-subdomains.prompt.md @@ -10,7 +10,7 @@ You are helping define business subdomains to create a clear domain model for th ## Process -**Read and follow** the complete process from [how-to-define-subdomains.md](.pair/knowledge/how-to/04-how-to-define-subdomains.md). +**Read and follow** the complete process from [how-to-define-subdomains.md](../../.pair/knowledge/how-to/04-how-to-define-subdomains.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/prioritize-initiatives.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/prioritize-initiatives.prompt.md index e627a8b5..55f15140 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/prioritize-initiatives.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/prioritize-initiatives.prompt.md @@ -10,7 +10,7 @@ You are helping create and prioritize strategic initiatives that translate PRD r ## Process -**Read and follow** the complete process from [how-to-create-and-prioritize-initiatives.md](.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md). +**Read and follow** the complete process from [how-to-create-and-prioritize-initiatives.md](../../.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md). **Execute the process exactly as documented**, including: - All phases and checkpoints diff --git a/packages/knowledge-hub/dataset/.github/prompts/refine-story.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/refine-story.prompt.md index ffaa1229..3a036eed 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/refine-story.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/refine-story.prompt.md @@ -12,7 +12,7 @@ If a story ID is provided (e.g., `/refine-story: story_id=STORY-123`), focus on ## Process -**Read and follow** the complete process from [how-to-refine-a-user-story.md](.pair/knowledge/how-to/08-how-to-refine-a-user-story.md). +**Read and follow** the complete process from [how-to-refine-a-user-story.md](../../.pair/knowledge/how-to/08-how-to-refine-a-user-story.md). **Execute the process exactly as documented**, including: diff --git a/packages/knowledge-hub/dataset/.github/prompts/subdomains.prompt.md b/packages/knowledge-hub/dataset/.github/prompts/subdomains.prompt.md index 1844b6c5..0b7fb683 100644 --- a/packages/knowledge-hub/dataset/.github/prompts/subdomains.prompt.md +++ b/packages/knowledge-hub/dataset/.github/prompts/subdomains.prompt.md @@ -10,7 +10,7 @@ You are helping define business subdomains to create a clear domain model for th ## Process -**Read and follow** the complete process from [how-to-define-subdomains.md](.pair/knowledge/how-to/04-how-to-define-subdomains.md). +**Read and follow** the complete process from [how-to-define-subdomains.md](../../.pair/knowledge/how-to/04-how-to-define-subdomains.md). **Execute the process exactly as documented**, including: - All phases and checkpoints diff --git a/packages/knowledge-hub/dataset/.pair/adoption/tech/README.md b/packages/knowledge-hub/dataset/.pair/adoption/tech/README.md index 4fe1229d..f6e14bd7 100644 --- a/packages/knowledge-hub/dataset/.pair/adoption/tech/README.md +++ b/packages/knowledge-hub/dataset/.pair/adoption/tech/README.md @@ -8,10 +8,10 @@ All adopted documents must: - Be written in **English** - Be **concise**: list only choices and decisions without explanations or rationale -- Reference the [knowledge-base](.pair/knowledge) for details, explanations, and background information +- Reference the [knowledge-base](../../knowledge) for details, explanations, and background information - Be **self-consistent** with compatible choices across library versions, user device targets, and deployment environments - Be **strict and prescriptive** with no ambiguity or open interpretation -- Address all relevant points from the [bootstrap-checklist](.pair/knowledge/assets/bootstrap-checklist.md) +- Address all relevant points from the [bootstrap-checklist](../../knowledge/assets/bootstrap-checklist.md) ## 📁 Document Categories @@ -35,7 +35,7 @@ These documents are **decision records**, not guidelines: - Contain only **validated choices** proposed by AI and approved by the team - Must be **implemented as written** with full compliance required -- Reference the [knowledge-base](.pair/knowledge) for detailed explanations +- Reference the [knowledge-base](../../knowledge) for detailed explanations - Must reflect the current project state and be kept up to date ## 🔄 Update Process @@ -52,21 +52,21 @@ Standards are updated during specific development phases: Detailed technical guidelines and explanations: -- [architecture/README.md](.pair/knowledge/guidelines/architecture/README.md) -- [02-code-design-guidelines.md](.pair/knowledge/guidelines/code-design/README.md) -- [technical-standards/README.md](.pair/knowledge/guidelines/technical-standards/README.md) -- [infrastructure/README.md](.pair/knowledge/guidelines/infrastructure/README.md) -- [05-ux-guidelines.md](.pair/knowledge/guidelines/user-experience/README.md) -- [06-definition-of-done.md](.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md) -- [07-testing-strategy.md](.pair/knowledge/guidelines/testing/test-strategy/README.md) -- [08-accessibility-guidelines.md](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md) -- [09-performance-guidelines.md](.pair/knowledge/guidelines/quality-assurance/performance/README.md) -- [10-security-guidelines.md](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- [11-observability-guidelines.md](.pair/knowledge/guidelines/observability/README.md) -- [README.md](.pair/knowledge/guidelines/README.md) – Knowledge Base Overview +- [architecture/README.md](../../knowledge/guidelines/architecture/README.md) +- [02-code-design-guidelines.md](../../knowledge/guidelines/code-design/README.md) +- [technical-standards/README.md](../../knowledge/guidelines/technical-standards/README.md) +- [infrastructure/README.md](../../knowledge/guidelines/infrastructure/README.md) +- [05-ux-guidelines.md](../../knowledge/guidelines/user-experience/README.md) +- [06-definition-of-done.md](../../knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md) +- [07-testing-strategy.md](../../knowledge/guidelines/testing/test-strategy/README.md) +- [08-accessibility-guidelines.md](../../knowledge/guidelines/quality-assurance/accessibility/README.md) +- [09-performance-guidelines.md](../../knowledge/guidelines/quality-assurance/performance/README.md) +- [10-security-guidelines.md](../../knowledge/guidelines/quality-assurance/security/README.md) +- [11-observability-guidelines.md](../../knowledge/guidelines/observability/README.md) +- [README.md](../../knowledge/guidelines/README.md) – Knowledge Base Overview ### Additional Resources -- **[Bootstrap Checklist](.pair/knowledge/assets/bootstrap-checklist.md)** – Project Setup & Bootstrap Checklist with all relevant questions the adopted standards must address +- **[Bootstrap Checklist](../../knowledge/assets/bootstrap-checklist.md)** – Project Setup & Bootstrap Checklist with all relevant questions the adopted standards must address - **[ADR](adr)** – Architecture Decision Records for significant changes -- **[Way of Working](.pair/knowledge/way-of-working.md)** – Development process and collaboration patterns +- **[Way of Working](../../knowledge/way-of-working.md)** – Development process and collaboration patterns diff --git a/packages/knowledge-hub/dataset/.pair/adoption/tech/architecture.md b/packages/knowledge-hub/dataset/.pair/adoption/tech/architecture.md index 553011e2..54496aae 100644 --- a/packages/knowledge-hub/dataset/.pair/adoption/tech/architecture.md +++ b/packages/knowledge-hub/dataset/.pair/adoption/tech/architecture.md @@ -2,7 +2,7 @@ ## Purpose -This document contains the **validated architectural decisions** for the project. It serves as the authoritative reference for all architectural patterns, system boundaries, and design principles that have been proposed by AI and validated by the development team during the **Strategic Preparation** phase outlined in the [way-of-working.md](.pair/knowledge/way-of-working.md). +This document contains the **validated architectural decisions** for the project. It serves as the authoritative reference for all architectural patterns, system boundaries, and design principles that have been proposed by AI and validated by the development team during the **Strategic Preparation** phase outlined in the [way-of-working.md](../../knowledge/way-of-working.md). **Who modifies this:** Development team with AI assistance (🤖🤝👨‍💻) during Strategic Preparation **When:** During PRD creation, bounded context definition, and architectural decision processes diff --git a/packages/knowledge-hub/dataset/.pair/adoption/tech/infrastructure.md b/packages/knowledge-hub/dataset/.pair/adoption/tech/infrastructure.md index 45516b21..562d5542 100644 --- a/packages/knowledge-hub/dataset/.pair/adoption/tech/infrastructure.md +++ b/packages/knowledge-hub/dataset/.pair/adoption/tech/infrastructure.md @@ -2,7 +2,7 @@ ## Purpose -This document defines the **validated infrastructure and deployment decisions** for the project. It serves as the authoritative specification for all DevOps practices, deployment strategies, and infrastructure patterns that have been proposed by AI and validated by the development team during the **Strategic Preparation** and **Continuous Value Delivery** phases outlined in the [way-of-working.md](.pair/knowledge/way-of-working.md). +This document defines the **validated infrastructure and deployment decisions** for the project. It serves as the authoritative specification for all DevOps practices, deployment strategies, and infrastructure patterns that have been proposed by AI and validated by the development team during the **Strategic Preparation** and **Continuous Value Delivery** phases outlined in the [way-of-working.md](../../knowledge/way-of-working.md). **Who modifies this:** Development team with AI assistance (🤖🤝👨‍💻) during infrastructure planning and deployment optimization **When:** During Strategic Preparation, Sprint Execution, and infrastructure evolution diff --git a/packages/knowledge-hub/dataset/.pair/adoption/tech/tech-stack.md b/packages/knowledge-hub/dataset/.pair/adoption/tech/tech-stack.md index 078390f0..47f8bd5f 100644 --- a/packages/knowledge-hub/dataset/.pair/adoption/tech/tech-stack.md +++ b/packages/knowledge-hub/dataset/.pair/adoption/tech/tech-stack.md @@ -2,7 +2,7 @@ ## Purpose -This document defines the **validated technology stack decisions** for the project. It serves as the authoritative reference for all technology choices (version included) that have been proposed by AI and validated by the development team during the **Strategic Preparation** and **Strategic Initiatives** phases outlined in the [way-of-working.md](.pair/knowledge/way-of-working.md). +This document defines the **validated technology stack decisions** for the project. It serves as the authoritative reference for all technology choices (version included) that have been proposed by AI and validated by the development team during the **Strategic Preparation** and **Strategic Initiatives** phases outlined in the [way-of-working.md](../../knowledge/way-of-working.md). **Who modifies this:** Development team with AI assistance (🤖🤝👨‍💻) **When:** During Strategic Preparation phase and when technology decisions are made diff --git a/packages/knowledge-hub/dataset/.pair/adoption/tech/ux-ui.md b/packages/knowledge-hub/dataset/.pair/adoption/tech/ux-ui.md index 13d2d9a2..c8d15d3c 100644 --- a/packages/knowledge-hub/dataset/.pair/adoption/tech/ux-ui.md +++ b/packages/knowledge-hub/dataset/.pair/adoption/tech/ux-ui.md @@ -2,7 +2,7 @@ ## Purpose -This document defines the **validated user experience and interface design decisions** for the project. It serves as the authoritative specification for all UX/UI patterns, design systems, and user interaction principles that have been proposed by AI and validated by the development team during the **Customer-Facing Iterations** phase outlined in the [way-of-working.md](.pair/knowledge/way-of-working.md). +This document defines the **validated user experience and interface design decisions** for the project. It serves as the authoritative specification for all UX/UI patterns, design systems, and user interaction principles that have been proposed by AI and validated by the development team during the **Customer-Facing Iterations** phase outlined in the [way-of-working.md](../../knowledge/way-of-working.md). **Who modifies this:** Development team with AI assistance (🤖🤝👨‍💻) during Epic breakdown and User Story refinement **When:** During customer-facing iterations, user story creation, and UX validation sessions diff --git a/packages/knowledge-hub/dataset/.pair/adoption/tech/way-of-working.md b/packages/knowledge-hub/dataset/.pair/adoption/tech/way-of-working.md index 8f7b104f..426e1a6e 100644 --- a/packages/knowledge-hub/dataset/.pair/adoption/tech/way-of-working.md +++ b/packages/knowledge-hub/dataset/.pair/adoption/tech/way-of-working.md @@ -2,8 +2,13 @@ ## Purpose -This document defines the **validated development practices and team workflows** for the project. It serves as the authoritative specification for all development methodologies, code review processes, and collaboration patterns that have been proposed by AI and validated by the development team throughout all phases outlined in the [way-of-working.md](.pair/knowledge/way-of-working.md). +This document defines the **validated development practices and team workflows** for the project. It serves as the authoritative specification for all development methodologies, code review processes, and collaboration patterns that have been proposed by AI and validated by the development team throughout all phases outlined in the [way-of-working.md](../../knowledge/way-of-working.md). -**Who modifies this:** Development team with AI assistance (🤖🤝👨‍💻) during process optimization and workflow refinement -**When:** During all phases - Strategic Preparation, Sprint Execution, and continuous process improvement +**Who modifies this:** Development team with AI assistance during process optimization and workflow refinement +**When:** During all phases - Strategic Preparation, Sprint Execution, and continuous process improvement **Authority:** All development activities must follow these validated practices + +## Quality Gates + +- `pnpm quality-gate` is the adopted project-level quality gate command. +- Quality gate includes: type checking (`ts:check`), testing (`test`), linting (`lint`), formatting (`prettier:fix`). diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/README.md index 20977509..3e962be9 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/README.md @@ -158,9 +158,9 @@ flowchart TD ## 🔗 Related Guidelines -- **[Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md)** - Code patterns implementing these architectural decisions -- **[Operations Guidelines](.pair/knowledge/guidelines/observability/README.md)** - Infrastructure deployment strategies for these patterns -- **[Quality Guidelines](.pair/knowledge/guidelines/quality-assurance/README.md)** - Quality criteria ensuring architectural integrity +- **[Code Design Guidelines](../code-design/README.md)** - Code patterns implementing these architectural decisions +- **[Operations Guidelines](../observability/README.md)** - Infrastructure deployment strategies for these patterns +- **[Quality Guidelines](../quality-assurance/README.md)** - Quality criteria ensuring architectural integrity ## 🎯 Quick Start diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/README.md index 038db76d..08522d28 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/README.md @@ -273,11 +273,11 @@ Low Complexity/Benefits → High Complexity/Benefits ## Related Patterns -- **[Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Domain modeling approach -- **[Bounded Context Patterns](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Context boundaries -- **[Integration Patterns](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Service integration -- **[Scaling Patterns](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Performance and scaling -- **[Deployment Architectures](.pair/knowledge/guidelines/architecture/deployment-architectures/README.md)** - Deployment strategies +- **[Domain-Driven Design](../design-patterns/README.md)** - Domain modeling approach +- **[Bounded Context Patterns](../design-patterns/README.md)** - Context boundaries +- **[Integration Patterns](../design-patterns/README.md)** - Service integration +- **[Scaling Patterns](../design-patterns/README.md)** - Performance and scaling +- **[Deployment Architectures](../deployment-architectures/README.md)** - Deployment strategies ## Implementation Guides diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/clean-architecture.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/clean-architecture.md index c4445d60..257749b3 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/clean-architecture.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/clean-architecture.md @@ -662,5 +662,5 @@ describe('CreateOrderUseCase', () => { ## Related Patterns - **[Hexagonal Architecture](hexagonal.md)** - Similar approach with ports/adapters -- **[Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Domain modeling approach +- **[Domain-Driven Design](../design-patterns/README.md)** - Domain modeling approach - **[CQRS](cqrs.md)** - Can be combined for read/write separation diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/hexagonal.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/hexagonal.md index e1d51a00..3433745a 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/hexagonal.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/hexagonal.md @@ -397,5 +397,5 @@ describe('PostgresOrderRepository', () => { ## Related Patterns - **[Clean Architecture](clean-architecture.md)** - Similar dependency inversion approach -- **[Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Domain modeling approach +- **[Domain-Driven Design](../design-patterns/README.md)** - Domain modeling approach - **[CQRS](cqrs.md)** - Can be combined for read/write separation diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/layer-architecture.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/layer-architecture.md index 58b74093..ad4ef47b 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/layer-architecture.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/architectural-patterns/layer-architecture.md @@ -440,4 +440,4 @@ When layered architecture becomes insufficient: - **[Hexagonal Architecture](hexagonal.md)** - Dependency inversion evolution - **[Clean Architecture](clean-architecture.md)** - Advanced layered approach -- **[Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/README.md)** - Domain modeling approach +- **[Domain-Driven Design](../design-patterns/README.md)** - Domain modeling approach diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md index acb124d8..687c937e 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md @@ -18,9 +18,9 @@ Define standardized processes for documenting, tracking, and reviewing architect **Out of Scope:** -- Specific architectural implementations (see [System Design](.pair/knowledge/guidelines/architecture/README.md)) -- Technical implementation details (see [Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md)) -- Infrastructure-specific decisions (see [Infrastructure](.pair/knowledge/guidelines/infrastructure/README.md)) +- Specific architectural implementations (see [System Design](../README.md)) +- Technical implementation details (see [Technical Standards](../../technical-standards/README.md)) +- Infrastructure-specific decisions (see [Infrastructure](../../infrastructure/README.md)) --- @@ -117,7 +117,7 @@ Document decisions that affect: ### Infrastructure-Specific ADR Template -For infrastructure and technology decisions, use the specialized process defined in [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md), which includes: +For infrastructure and technology decisions, use the specialized process defined in [Infrastructure Guidelines](../../infrastructure/README.md), which includes: - Infrastructure-specific ADR considerations - Service addition workflow and validation @@ -251,15 +251,15 @@ This practice supports the **Definition of Done** requirements: **Core Architecture References:** -- **[System Design Practice](.pair/knowledge/guidelines/architecture/README.md)** - Architectural patterns and design principles -- **[Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md)** - Technology stack decisions and standards -- **[Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md)** - Infrastructure-specific decision processes +- **[System Design Practice](../README.md)** - Architectural patterns and design principles +- **[Technical Standards](../../technical-standards/README.md)** - Technology stack decisions and standards +- **[Infrastructure Guidelines](../../infrastructure/README.md)** - Infrastructure-specific decision processes **Quality and Process References:** -- **[Standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md)** - Quality criteria for architectural decisions -- **[Project Management](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - Decision tracking within project workflows -- **[Testing Strategy](.pair/knowledge/guidelines/testing/README.md)** - Testing approaches for architectural validation +- **[Standards](../../quality-assurance/quality-standards/README.md)** - Quality criteria for architectural decisions +- **[Project Management](../../collaboration/project-management-tool/README.md)** - Decision tracking within project workflows +- **[Testing Strategy](../../testing/README.md)** - Testing approaches for architectural validation --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/desktop-self-hosted.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/desktop-self-hosted.md index f58f9bbb..0c799d37 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/desktop-self-hosted.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/desktop-self-hosted.md @@ -212,10 +212,10 @@ services: ## Cross-References -- **[Project Constraints](.pair/knowledge/guidelines/architecture/project-constraints/README.md)** - Desktop-only and self-hosting constraints -- **[LLM Integration](.pair/knowledge/guidelines/architecture/llm-integration/README.md)** - External service integration patterns +- **[Project Constraints](../project-constraints/README.md)** - Desktop-only and self-hosting constraints +- **[LLM Integration](../llm-integration/README.md)** - External service integration patterns - **[Structured Monolith](structured-monolith.md)** - Simple deployment architecture -- **[Tech Stack](.pair/knowledge/guidelines/technical-standards/technology-stack/README.md)** - Technology choices +- **[Tech Stack](../../technical-standards/technology-stack/README.md)** - Technology choices ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/hybrid.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/hybrid.md index fc38d400..fb8b1ac1 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/hybrid.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/hybrid.md @@ -257,4 +257,4 @@ export class BFFOrchestrator { - [Structured Monolith](structured-monolith.md) - Starting point - [Microservices](microservices.md) - Target for some components - [Serverless](serverless.md) - Event-driven components -- [Integration Patterns](.pair/knowledge/guidelines/architecture/design-patterns/README.md) - Communication strategies +- [Integration Patterns](../design-patterns/README.md) - Communication strategies diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/microservices.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/microservices.md index dafa76f4..06220d0d 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/microservices.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/microservices.md @@ -170,5 +170,5 @@ export class OrderService { - [Modular Monolith](modular-monolith.md) - Previous evolution step - [Serverless](serverless.md) - Function-based alternative -- [API Gateway](.pair/knowledge/guidelines/architecture/design-patterns/README.md) - Service composition pattern -- [Circuit Breaker](.pair/knowledge/guidelines/architecture/README.md) - Resilience pattern +- [API Gateway](../design-patterns/README.md) - Service composition pattern +- [Circuit Breaker](../README.md) - Resilience pattern diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/modular-monolith.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/modular-monolith.md index 332a7905..9de99c6b 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/modular-monolith.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/modular-monolith.md @@ -152,5 +152,5 @@ export class InternalEventBus { - [Structured Monolith](structured-monolith.md) - Simpler alternative - [Microservices](microservices.md) - Next evolution step -- [Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/README.md) - Domain modeling approach -- [Event Sourcing](.pair/knowledge/guidelines/architecture/architectural-patterns/event-sourcing.md) - Event-based persistence +- [Domain-Driven Design](../design-patterns/README.md) - Domain modeling approach +- [Event Sourcing](../architectural-patterns/event-sourcing.md) - Event-based persistence diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/serverless.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/serverless.md index ca83b998..b3ff4357 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/serverless.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/serverless.md @@ -157,7 +157,7 @@ export const handleOrderCreated = async ( ## Related Patterns -- [Event-Driven Architecture](.pair/knowledge/guidelines/architecture/design-patterns/README.md) - Event communication patterns +- [Event-Driven Architecture](../design-patterns/README.md) - Event communication patterns - [Microservices](microservices.md) - Service-based alternative -- [CQRS](.pair/knowledge/guidelines/architecture/architectural-patterns/cqrs.md) - Command-query separation -- [Circuit Breaker](.pair/knowledge/guidelines/architecture/README.md) - Resilience patterns +- [CQRS](../architectural-patterns/cqrs.md) - Command-query separation +- [Circuit Breaker](../README.md) - Resilience patterns diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/structured-monolith.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/structured-monolith.md index 06edad18..88885f0a 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/structured-monolith.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/deployment-architectures/structured-monolith.md @@ -122,4 +122,4 @@ export class Application { - [Modular Monolith](modular-monolith.md) - Next evolution step - [Microservices](microservices.md) - Distributed alternative -- [Layered Architecture](.pair/knowledge/guidelines/architecture/architectural-patterns/layer-architecture.md) - Internal organization pattern +- [Layered Architecture](../architectural-patterns/layer-architecture.md) - Internal organization pattern diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md index cfe6b151..da541dc1 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md @@ -62,5 +62,5 @@ src/ - **[Strategic Subdomain Definition](strategic-subdomain-definition.md)** - Comprehensive subdomain identification and classification guide - **[Bounded Contexts](bounded-contexts.md)** - Technical implementation boundaries for subdomains - **[System Design README](README.md)** - Overall system design principles -- **[Decision Records](.pair/knowledge/guidelines/architecture/decision-frameworks/README.md)** - ADR process for DDD decisions -- **[Code Design](.pair/knowledge/guidelines/code-design/README.md)** - Implementation patterns for DDD +- **[Decision Records](../decision-frameworks/README.md)** - ADR process for DDD decisions +- **[Code Design](../../code-design/README.md)** - Implementation patterns for DDD diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/integration-patterns.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/integration-patterns.md index b78d0f76..28a23dfc 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/integration-patterns.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/integration-patterns.md @@ -114,5 +114,5 @@ interface UserRegisteredEvent extends DomainEvent { ## Related Documents - **[System Design README](README.md)** - Overall system design principles -- **[Bounded Context Patterns](.pair/knowledge/guidelines/architecture/README.md)** - Context boundary implementation -- **[Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md)** - Infrastructure integration patterns +- **[Bounded Context Patterns](../README.md)** - Context boundary implementation +- **[Infrastructure Guidelines](../../infrastructure/README.md)** - Infrastructure integration patterns diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md index da49d1cc..2fa437c2 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md @@ -285,5 +285,5 @@ All subdomains can be classified into three strategic categories that drive deve ### Decision Framework -- **[Architecture Decision Records](.pair/knowledge/guidelines/architecture/decision-frameworks/README.md)** - Document subdomain classification decisions -- **[Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md)** - Implementation patterns for subdomain boundaries +- **[Architecture Decision Records](../decision-frameworks/README.md)** - Document subdomain classification decisions +- **[Code Design Guidelines](../../code-design/README.md)** - Implementation patterns for subdomain boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/llm-integration/performance-security.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/llm-integration/performance-security.md index 41600af2..3f81d929 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/llm-integration/performance-security.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/llm-integration/performance-security.md @@ -584,7 +584,7 @@ class PerformanceMonitor { - **[LLM Services](ai-workflows.md)** - LLM performance optimization and security - **[RAG Architecture](rag-architecture.md)** - RAG performance and security considerations - **[Data Architecture](vector-databases.md)** - Data security and performance -- **[Project Constraints](.pair/knowledge/guidelines/architecture/project-constraints/README.md)** - Security and performance constraints +- **[Project Constraints](../project-constraints/README.md)** - Security and performance constraints ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/README.md index 357870b5..f8214a8f 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/README.md @@ -39,9 +39,9 @@ Define and document the specific architectural constraints that guide all system ## Cross-References -- **[Deployment Architectures](.pair/knowledge/guidelines/architecture/deployment-architectures/README.md)** - Self-hosted deployment patterns -- **[Tech Stack](.pair/adoption/tech/tech-stack.md)** - Specific technology choices -- **[Way of Working](.pair/adoption/tech/way-of-working.md)** - Process constraints and decisions +- **[Deployment Architectures](../deployment-architectures/README.md)** - Self-hosted deployment patterns +- **[Tech Stack](../../../../adoption/tech/tech-stack.md)** - Specific technology choices +- **[Way of Working](../../../../adoption/tech/way-of-working.md)** - Process constraints and decisions ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/deployment-constraints.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/deployment-constraints.md index 96de82c8..b162c829 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/deployment-constraints.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/deployment-constraints.md @@ -206,9 +206,9 @@ Decision-making frameworks and implementation priorities for project architectur ## Cross-References - **[Team Constraints](team-constraints.md)** - Team-based decision factors -- **[Technology Constraints](.pair/knowledge/guidelines/architecture/README.md)** - Technology selection criteria -- **[Tech Stack](.pair/adoption/tech/tech-stack.md)** - Current technology choices -- **[Architecture Patterns](.pair/knowledge/guidelines/architecture/architectural-patterns/README.md)** - Pattern selection guidance +- **[Technology Constraints](../README.md)** - Technology selection criteria +- **[Tech Stack](../../../../adoption/tech/tech-stack.md)** - Current technology choices +- **[Architecture Patterns](../architectural-patterns/README.md)** - Pattern selection guidance ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/platform-constraints.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/platform-constraints.md index 958d0f53..45b3895c 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/platform-constraints.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/platform-constraints.md @@ -146,8 +146,8 @@ Constraints related to platform targeting and deployment preferences for the pro ## Cross-References - **[Team Constraints](team-constraints.md)** - Small team deployment considerations -- **[Technology Constraints](.pair/knowledge/guidelines/architecture/README.md)** - Technology selection criteria -- **[Deployment Architectures](.pair/knowledge/guidelines/architecture/deployment-architectures/README.md)** - Specific deployment patterns +- **[Technology Constraints](../README.md)** - Technology selection criteria +- **[Deployment Architectures](../deployment-architectures/README.md)** - Specific deployment patterns ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/team-constraints.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/team-constraints.md index 2616c9db..6719b453 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/team-constraints.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/architecture/project-constraints/team-constraints.md @@ -113,8 +113,8 @@ Architectural constraints specific to small team development and rapid deploymen ## Cross-References - **[Platform Constraints](platform-constraints.md)** - Platform and deployment constraints -- **[Implementation Guidelines](.pair/knowledge/guidelines/architecture/README.md)** - Decision making frameworks -- **[Way of Working](.pair/adoption/tech/way-of-working.md)** - Process and workflow decisions +- **[Implementation Guidelines](../README.md)** - Decision making frameworks +- **[Way of Working](../../../../adoption/tech/way-of-working.md)** - Process and workflow decisions ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/README.md index fe732ed0..b94aaaa8 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/README.md @@ -40,7 +40,7 @@ This framework does not cover: **[Team](team/README.md)** - Team structure, roles, responsibility frameworks, and communication protocols for distributed teams -**[Communication Protocols](.pair/knowledge/guidelines/README.md)** - Communication standards for different types of interactions, meeting management, and documentation standards +**[Communication Protocols](../README.md)** - Communication standards for different types of interactions, meeting management, and documentation standards ### Process Automation and Efficiency diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/automation/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/automation/README.md index 074c51e5..30ef6411 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/automation/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/automation/README.md @@ -172,7 +172,7 @@ This section covers automation approaches for project management workflows, deve ## Related Topics -- **[../issue-management/](.pair/knowledge/guidelines/collaboration/issue-management/README.md)** - Automated issue workflows -- **[../project-tracking/](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** - Automated tracking and reporting -- **[../project-management-tool/](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - Tool-specific automation setup -- **[../communication-protocols/](.pair/knowledge/guidelines/collaboration/team/README.md)** - Automated communication workflows +- **[../issue-management/](../issue-management/README.md)** - Automated issue workflows +- **[../project-tracking/](../project-tracking/README.md)** - Automated tracking and reporting +- **[../project-management-tool/](../project-management-tool/README.md)** - Tool-specific automation setup +- **[../communication-protocols/](../team/README.md)** - Automated communication workflows diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/estimation/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/estimation/README.md index ae1bcc10..a0bbdb89 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/estimation/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/estimation/README.md @@ -299,6 +299,6 @@ Start: What type of project are you estimating? ## Related Documents -- **[methodology/](.pair/knowledge/guidelines/collaboration/methodology/README.md)** - Integration with Agile, Waterfall, and hybrid methodologies -- **[project-tracking/](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** - Tracking estimation accuracy and project progress -- **[project-management-tool/](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - Tool-specific estimation implementations +- **[methodology/](../methodology/README.md)** - Integration with Agile, Waterfall, and hybrid methodologies +- **[project-tracking/](../project-tracking/README.md)** - Tracking estimation accuracy and project progress +- **[project-management-tool/](../project-management-tool/README.md)** - Tool-specific estimation implementations diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/README.md index bfa9358e..22164c09 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/README.md @@ -132,7 +132,7 @@ The **IssueManagementOrchestrator** provides comprehensive issue handling throug ### With Project Tracking -**→ See [../project-tracking/](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** +**→ See [../project-tracking/](../project-tracking/README.md)** - Issue hierarchy and relationships - Progress tracking and reporting @@ -140,7 +140,7 @@ The **IssueManagementOrchestrator** provides comprehensive issue handling throug ### With Automation -**→ See [../automation/](.pair/knowledge/guidelines/collaboration/automation/README.md)** +**→ See [../automation/](../automation/README.md)** - Automated issue creation and updates - Status synchronization rules @@ -148,7 +148,7 @@ The **IssueManagementOrchestrator** provides comprehensive issue handling throug ### With Estimation -**→ See [../estimation/](.pair/knowledge/guidelines/collaboration/estimation/README.md)** +**→ See [../estimation/](../estimation/README.md)** - Issue sizing and effort estimation - Complexity assessment workflows @@ -156,6 +156,6 @@ The **IssueManagementOrchestrator** provides comprehensive issue handling throug ## Related Topics -- **[../project-management-tool/](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - Tool setup and configuration -- **[../assets/](.pair/knowledge/guidelines/collaboration/templates/README.md)** - Issue templates and resources -- **[../communication-protocols/](.pair/knowledge/guidelines/collaboration/team/README.md)** - Communication around issues +- **[../project-management-tool/](../project-management-tool/README.md)** - Tool setup and configuration +- **[../assets/](../templates/README.md)** - Issue templates and resources +- **[../communication-protocols/](../team/README.md)** - Communication around issues diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md index f0ebe7f7..e46633f2 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md @@ -240,6 +240,6 @@ jobs: ## Related Documents -- **[.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md](.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md)** - Project progress tracking -- **[.pair/knowledge/guidelines/collaboration/automation/filesystem-automation.md](.pair/knowledge/guidelines/collaboration/automation/filesystem-automation.md)** - Automation workflows +- **[.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md](../project-tracking/filesystem-tracking.md)** - Project progress tracking +- **[.pair/knowledge/guidelines/collaboration/automation/filesystem-automation.md](../automation/filesystem-automation.md)** - Automation workflows - **[github-issues.md](github-issues.md)** - Comparison with GitHub Issues workflow diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md index 9f1245f5..ff7d8ae2 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md @@ -564,7 +564,7 @@ gh issue list --milestone "[Sprint Name]" ## Related Topics -- **[.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md](.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md)** - Project board integration -- **[.pair/knowledge/guidelines/collaboration/automation/github-automation.md](.pair/knowledge/guidelines/collaboration/automation/github-automation.md)** - Automated workflows -- **[.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md](.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md)** - Overall GitHub setup -- **[.pair/knowledge/guidelines/collaboration/project-tracking/README.md](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** - Board setup and optimization strategies +- **[.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md](../project-tracking/github-tracking.md)** - Project board integration +- **[.pair/knowledge/guidelines/collaboration/automation/github-automation.md](../automation/github-automation.md)** - Automated workflows +- **[.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md](../project-management-tool/github-implementation.md)** - Overall GitHub setup +- **[.pair/knowledge/guidelines/collaboration/project-tracking/README.md](../project-tracking/README.md)** - Board setup and optimization strategies diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/methodology/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/methodology/README.md index d2b3dfc6..b93fe08d 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/methodology/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/methodology/README.md @@ -837,13 +837,13 @@ Each methodology file includes: ## Related Topics -- **[Project Management Tools](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)**: Tool support for different methodologies -- **[Estimation](.pair/knowledge/guidelines/collaboration/estimation/README.md)**: Estimation approaches by methodology -- **[Board Management](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)**: Board configuration for different methodologies +- **[Project Management Tools](../project-management-tool/README.md)**: Tool support for different methodologies +- **[Estimation](../estimation/README.md)**: Estimation approaches by methodology +- **[Board Management](../project-tracking/README.md)**: Board configuration for different methodologies - Common pitfalls and mitigation strategies ## Related Topics -- **[../project-management-tool/](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - Tool implementations for each methodology -- **[../estimation/](.pair/knowledge/guidelines/collaboration/estimation/README.md)** - Estimation approaches by methodology -- **[.pair/knowledge/guidelines/collaboration/team/role-responsibilities.md](.pair/knowledge/guidelines/collaboration/team/role-responsibilities.md)** - Role definitions within methodologies +- **[../project-management-tool/](../project-management-tool/README.md)** - Tool implementations for each methodology +- **[../estimation/](../estimation/README.md)** - Estimation approaches by methodology +- **[.pair/knowledge/guidelines/collaboration/team/role-responsibilities.md](../team/role-responsibilities.md)** - Role definitions within methodologies diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/filesystem-implementation.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/filesystem-implementation.md index 35c71acd..5146d1bd 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/filesystem-implementation.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/filesystem-implementation.md @@ -89,7 +89,7 @@ ls ../guidelines/collaboration/templates/ ### Issue Management -**→ See [../issue-management/](.pair/knowledge/guidelines/collaboration/issue-management/README.md)** +**→ See [../issue-management/](../issue-management/README.md)** - Local issue tracking with markdown files - Directory-based status management @@ -98,7 +98,7 @@ ls ../guidelines/collaboration/templates/ ### Project Tracking -**→ See [../project-tracking/](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** +**→ See [../project-tracking/](../project-tracking/README.md)** - Hierarchical directory structure - Status tracking via file location @@ -107,7 +107,7 @@ ls ../guidelines/collaboration/templates/ ### Automation -**→ See [../automation/](.pair/knowledge/guidelines/collaboration/automation/README.md)** +**→ See [../automation/](../automation/README.md)** - Shell script automation - File operation automation @@ -125,7 +125,7 @@ ls ../guidelines/collaboration/templates/ ### Communication -**→ See [../communication-protocols/](.pair/knowledge/guidelines/README.md)** +**→ See [../communication-protocols/](../../README.md)** - Documentation-based communication - Local changelog management @@ -134,7 +134,7 @@ ls ../guidelines/collaboration/templates/ ### Estimation Integration -**→ See [../estimation/](.pair/knowledge/guidelines/collaboration/estimation/README.md)** +**→ See [../estimation/](../estimation/README.md)** - File-based estimation tracking - Simple effort recording in metadata @@ -143,7 +143,7 @@ ls ../guidelines/collaboration/templates/ ### Methodology Integration -**→ See [../methodology/](.pair/knowledge/guidelines/collaboration/methodology/README.md)** +**→ See [../methodology/](../methodology/README.md)** - Scrum integration with filesystem structure - Kanban workflow with directory states @@ -580,10 +580,10 @@ Add review tasks to the story file: ## Related Tools -- **Methodology Selection**: [methodology-selection-guide.md](.pair/knowledge/guidelines/collaboration/methodology/README.md) -- **Project Tracking**: [project-tracking/README.md](.pair/knowledge/guidelines/collaboration/project-tracking/README.md) +- **Methodology Selection**: [methodology-selection-guide.md](../methodology/README.md) +- **Project Tracking**: [project-tracking/README.md](../project-tracking/README.md) - **GitHub Integration**: [github-implementation.md](github-implementation.md) -- **Templates**: [assets/README.md](.pair/knowledge/guidelines/collaboration/templates/README.md) +- **Templates**: [assets/README.md](../templates/README.md) --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md index 52fda3b8..42bebbfa 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md @@ -36,7 +36,7 @@ npm install -g @github/github-mcp-server ### Issue Management -**→ See [../issue-management/](.pair/knowledge/guidelines/collaboration/issue-management/README.md)** +**→ See [../issue-management/](../issue-management/README.md)** - GitHub Issues setup and configuration - Label management and templates @@ -45,7 +45,7 @@ npm install -g @github/github-mcp-server ### Project Tracking -**→ See [../project-tracking/](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** +**→ See [../project-tracking/](../project-tracking/README.md)** - GitHub Projects board configuration - Custom fields setup (Priority, Type, Status) @@ -54,7 +54,7 @@ npm install -g @github/github-mcp-server ### Automation -**→ See [../automation/](.pair/knowledge/guidelines/collaboration/automation/README.md)** +**→ See [../automation/](../automation/README.md)** - GitHub Actions workflows - MCP integration for AI-assisted management @@ -63,7 +63,7 @@ npm install -g @github/github-mcp-server ### Board Management -**→ See [.pair/knowledge/guidelines/collaboration/project-tracking/README.md](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** +**→ See [.pair/knowledge/guidelines/collaboration/project-tracking/README.md](../project-tracking/README.md)** - Board layout and column configuration - Workflow optimization @@ -72,7 +72,7 @@ npm install -g @github/github-mcp-server ### Communication -**→ See [.pair/knowledge/guidelines/collaboration/team/README.md](.pair/knowledge/guidelines/collaboration/team/README.md)** +**→ See [.pair/knowledge/guidelines/collaboration/team/README.md](../team/README.md)** - Pull request workflows and reviews - GitHub Discussions integration @@ -81,7 +81,7 @@ npm install -g @github/github-mcp-server ### Estimation Integration -**→ See [../estimation/](.pair/knowledge/guidelines/collaboration/estimation/README.md)** +**→ See [../estimation/](../estimation/README.md)** - GitHub-compatible estimation approaches - Story point tracking in custom fields @@ -90,7 +90,7 @@ npm install -g @github/github-mcp-server ### Methodology Integration -**→ See [../methodology/](.pair/knowledge/guidelines/collaboration/methodology/README.md)** +**→ See [../methodology/](../methodology/README.md)** - Scrum integration with GitHub Projects - Kanban workflow implementation @@ -102,7 +102,7 @@ npm install -g @github/github-mcp-server ### Automation -**→ See [.pair/knowledge/guidelines/collaboration/automation/github-automation.md](.pair/knowledge/guidelines/collaboration/automation/github-automation.md)** +**→ See [.pair/knowledge/guidelines/collaboration/automation/github-automation.md](../automation/github-automation.md)** - GitHub Actions workflows - MCP integration for AI-assisted management @@ -111,7 +111,7 @@ npm install -g @github/github-mcp-server ### Board Management -**→ See [board-management.md](.pair/knowledge/guidelines/collaboration/project-tracking/README.md)** +**→ See [board-management.md](../project-tracking/README.md)** - Board layout and column configuration - Workflow optimization @@ -120,7 +120,7 @@ npm install -g @github/github-mcp-server ### Communication -**→ See [../communication-protocols/](.pair/knowledge/guidelines/collaboration/team/README.md)** +**→ See [../communication-protocols/](../team/README.md)** - Pull request workflows and reviews - GitHub Discussions integration @@ -129,7 +129,7 @@ npm install -g @github/github-mcp-server ### Estimation Integration -**→ See [../estimation/](.pair/knowledge/guidelines/collaboration/estimation/README.md)** +**→ See [../estimation/](../estimation/README.md)** - GitHub-compatible estimation approaches - Story point tracking in custom fields @@ -164,7 +164,7 @@ npm install -g @github/github-mcp-server ## Integration with Methodologies -**→ See [../methodology/](.pair/knowledge/guidelines/collaboration/methodology/README.md)** +**→ See [../methodology/](../methodology/README.md)** ### Scrum Integration diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/README.md index 8c8dea12..d1b90c0f 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/README.md @@ -230,7 +230,7 @@ This project tracking framework ensures systematic progress monitoring, predicti ### With Issue Management -**→ See [../issue-management/](.pair/knowledge/guidelines/collaboration/issue-management/README.md)** +**→ See [../issue-management/](../issue-management/README.md)** - Issue status integration - Priority and type tracking @@ -238,7 +238,7 @@ This project tracking framework ensures systematic progress monitoring, predicti ### With Estimation -**→ See [../estimation/](.pair/knowledge/guidelines/collaboration/estimation/README.md)** +**→ See [../estimation/](../estimation/README.md)** - Effort tracking and comparison - Velocity calculation inputs @@ -254,7 +254,7 @@ This project tracking framework ensures systematic progress monitoring, predicti ### With Automation -**→ See [../automation/](.pair/knowledge/guidelines/collaboration/automation/README.md)** +**→ See [../automation/](../automation/README.md)** - Automated progress updates - Status synchronization @@ -285,6 +285,6 @@ This project tracking framework ensures systematic progress monitoring, predicti ## Related Topics -- **[../methodology/](.pair/knowledge/guidelines/collaboration/methodology/README.md)** - Methodology-specific tracking approaches -- **[../project-management-tool/](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - Tool setup and configuration +- **[../methodology/](../methodology/README.md)** - Methodology-specific tracking approaches +- **[../project-management-tool/](../project-management-tool/README.md)** - Tool setup and configuration - **[README.md](README.md)** - Board and backlog management practices diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md index 9722a2e2..e2dd86ab 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/filesystem-tracking.md @@ -347,6 +347,6 @@ Date,Completed Points,Team Size,Velocity per Person ## Related Documents -- **[.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md](.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md)** - Issue tracking implementation -- **[.pair/knowledge/guidelines/collaboration/automation/filesystem-automation.md](.pair/knowledge/guidelines/collaboration/automation/filesystem-automation.md)** - Automation workflows +- **[.pair/knowledge/guidelines/collaboration/issue-management/filesystem-issues.md](../issue-management/filesystem-issues.md)** - Issue tracking implementation +- **[.pair/knowledge/guidelines/collaboration/automation/filesystem-automation.md](../automation/filesystem-automation.md)** - Automation workflows - **[github-tracking.md](github-tracking.md)** - Comparison with GitHub-based tracking diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md index 6e7c586b..f475e61e 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/project-tracking/github-tracking.md @@ -293,7 +293,7 @@ gh project item-list [project_number] --format json > project_data.json ### With Issue Management -**→ See [.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md](.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md)** +**→ See [.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md](../issue-management/github-issues.md)** - Automatic issue addition to boards - Label synchronization with custom fields @@ -301,7 +301,7 @@ gh project item-list [project_number] --format json > project_data.json ### With Automation -**→ See [.pair/knowledge/guidelines/collaboration/automation/github-automation.md](.pair/knowledge/guidelines/collaboration/automation/github-automation.md)** +**→ See [.pair/knowledge/guidelines/collaboration/automation/github-automation.md](../automation/github-automation.md)** - Automated board updates - Status synchronization rules @@ -325,6 +325,6 @@ gh project item-list [project_number] --format json > project_data.json ## Related Topics -- **[.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md](.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md)** - Issue creation and management -- **[.pair/knowledge/guidelines/collaboration/automation/github-automation.md](.pair/knowledge/guidelines/collaboration/automation/github-automation.md)** - Automation setup -- **[github-implementation.md](.pair/knowledge/guidelines/collaboration/project-management-tool/github-implementation.md)** - Overall GitHub configuration +- **[.pair/knowledge/guidelines/collaboration/issue-management/github-issues.md](../issue-management/github-issues.md)** - Issue creation and management +- **[.pair/knowledge/guidelines/collaboration/automation/github-automation.md](../automation/github-automation.md)** - Automation setup +- **[github-implementation.md](../project-management-tool/github-implementation.md)** - Overall GitHub configuration diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/templates/adl-template.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/templates/adl-template.md new file mode 100644 index 00000000..23e3bfa5 --- /dev/null +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/templates/adl-template.md @@ -0,0 +1,34 @@ +# Decision: [Decision Title] + +## Date + +YYYY-MM-DD + +## Status + +[Active | Superseded by ADL-YYYY-MM-DD-] + +## Category + +[Library Choice | Convention Adoption | Tooling Preference | Process Decision] + +## Context + +[What prompted this decision — the problem, need, or opportunity that required a choice.] + +## Decision + +[What was decided and why. Be specific: name the library/convention/tool chosen and the rationale.] + +## Alternatives Considered + +- **[Alternative 1]**: [Why it was not chosen] +- **[Alternative 2]**: [Why it was not chosen] + +## Consequences + +[Impact on the project — what changes as a result of this decision. Include any migration steps if replacing an existing choice.] + +## Adoption Impact + +[Which adoption files must be updated — e.g., `adoption/tech/tech-stack.md` for a new library, `adoption/tech/way-of-working.md` for a process change. List each file and the specific change required.] diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/templates/adr-template.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/templates/adr-template.md new file mode 100644 index 00000000..30f9e80a --- /dev/null +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/collaboration/templates/adr-template.md @@ -0,0 +1,52 @@ +# ADR: [Decision Title] + +## Status + +[Proposed | Accepted | Deprecated | Superseded by ADR-YYYY-MM-DD-] + +## Date + +YYYY-MM-DD + +## Context + +- [Business requirement or technical challenge that triggered this decision] +- [Current system state and limitations] +- [Stakeholders and their concerns] +- [Timeline and resource constraints] + +## Options Considered + +### Option 1: [Name] + +- **Description**: [Brief description] +- **Pros**: [Advantages] +- **Cons**: [Disadvantages] + +### Option 2: [Name] + +- **Description**: [Brief description] +- **Pros**: [Advantages] +- **Cons**: [Disadvantages] + +## Decision + +[Chosen solution and justification. Explain WHY this option was selected over alternatives.] + +## Consequences + +### Benefits + +- [Positive outcomes and advantages] +- [Problem resolution] +- [Long-term benefits] + +### Trade-offs and Limitations + +- [Known limitations and constraints] +- [Technical debt introduced] +- [Future implications] + +## Adoption Impact + +[Which adoption files must be updated to reflect this decision — e.g., `adoption/tech/architecture.md`, `adoption/tech/tech-stack.md`. List each file and the specific change required.] diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/README.md index 023156a3..bd9322fc 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/README.md @@ -169,10 +169,10 @@ Starting infrastructure implementation? ## 🔗 Related Knowledge Areas -- **[Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md)** - Application architecture and development practices -- **[Quality Assurance](.pair/knowledge/guidelines/quality-assurance/README.md)** - Testing strategies and quality frameworks -- **[Observability](.pair/knowledge/guidelines/observability/README.md)** - Operational practices and monitoring strategies -- **[Quality Assurance Guidelines](.pair/knowledge/guidelines/quality-assurance/README.md)** - Security practices and compliance frameworks +- **[Code Design Guidelines](../code-design/README.md)** - Application architecture and development practices +- **[Quality Assurance](../quality-assurance/README.md)** - Testing strategies and quality frameworks +- **[Observability](../observability/README.md)** - Operational practices and monitoring strategies +- **[Quality Assurance Guidelines](../quality-assurance/README.md)** - Security practices and compliance frameworks ## 📈 Infrastructure Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md index d3e74c78..ad1a0206 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md @@ -271,10 +271,10 @@ Implementing CI/CD strategy? ## 🔗 Related Practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control -- **[Deployment Patterns](.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md)** - Application deployment strategies and automation -- **[Environments](.pair/knowledge/guidelines/infrastructure/environments/README.md)** - Environment management and consistency strategies -- **[Testing Infrastructure](.pair/knowledge/guidelines/infrastructure/testing-infrastructure/README.md)** - Testing environment and automation infrastructure +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[Deployment Patterns](../deployment-patterns/README.md)** - Application deployment strategies and automation +- **[Environments](../environments/README.md)** - Environment management and consistency strategies +- **[Testing Infrastructure](../testing-infrastructure/README.md)** - Testing environment and automation infrastructure ## 📈 CI/CD Strategy Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md index 3f92ab91..e5a234fb 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md @@ -233,8 +233,8 @@ Selecting cloud provider strategy? ## 🔗 Related Practices -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud service selection and integration patterns -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[Cloud Services](../cloud-services/README.md)** - Cloud service selection and integration patterns +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control - **[Cost Optimization](cost-optimization.md)** - Cloud cost optimization strategies and tools - **[Multi-Cloud Strategy](multi-cloud.md)** - Multi-cloud architecture and governance diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-services/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-services/README.md index 219bfc6d..1eced7a8 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-services/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/cloud-services/README.md @@ -541,10 +541,10 @@ class CostOptimizer { ## 🔗 Related Practices -- **[Cloud Providers](.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md)** - Strategic cloud platform selection and implementation -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Environments](.pair/knowledge/guidelines/infrastructure/environments/README.md)** - Environment management and consistency strategies +- **[Cloud Providers](../cloud-providers/README.md)** - Strategic cloud platform selection and implementation +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Environments](../environments/README.md)** - Environment management and consistency strategies ## 📈 Cloud Services Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md index 4297185a..3339552f 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md @@ -374,10 +374,10 @@ This container orchestration guide provides a comprehensive framework for enterp ## 🔗 Related Practices -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud service selection and integration patterns -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Deployment Patterns](.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md)** - Application deployment strategies and automation +- **[Cloud Services](../cloud-services/README.md)** - Cloud service selection and integration patterns +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Deployment Patterns](../deployment-patterns/README.md)** - Application deployment strategies and automation ## 📈 Container Orchestration Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md index 9fed0ea8..36213d77 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md @@ -194,10 +194,10 @@ Selecting deployment strategy? ## 🔗 Related Practices -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control -- **[Container Orchestration](.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md)** - Container platform strategies and implementation -- **[Environments](.pair/knowledge/guidelines/infrastructure/environments/README.md)** - Environment management and consistency strategies +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[Container Orchestration](../container-orchestration/README.md)** - Container platform strategies and implementation +- **[Environments](../environments/README.md)** - Environment management and consistency strategies ## 📈 Deployment Pattern Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/deployment-strategies.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/deployment-strategies.md index e75870ef..c0e5972e 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/deployment-strategies.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/deployment-strategies.md @@ -491,10 +491,10 @@ resource "aws_appautoscaling_target" "app_scale_target" { ## 🔗 Related Practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure provisioning and management -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Environment Management](.pair/knowledge/guidelines/infrastructure/environments/README.md)** - Environment configuration and consistency -- **[Monitoring and Observability](.pair/knowledge/guidelines/observability/README.md)** - Production monitoring and alerting +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure provisioning and management +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Environment Management](../environments/README.md)** - Environment configuration and consistency +- **[Monitoring and Observability](../../observability/README.md)** - Production monitoring and alerting --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/monitoring.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/monitoring.md index 1ade3b9d..51a1d0c0 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/monitoring.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/monitoring.md @@ -478,10 +478,10 @@ resource "datadog_monitor" "deployment_success_rate" { ## 🔗 Related Practices -- **[Operations Monitoring](.pair/knowledge/guidelines/observability/README.md)** - General application and infrastructure monitoring -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Operations Monitoring](../../observability/README.md)** - General application and infrastructure monitoring +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices - **[Deployment Strategies](deployment-strategies.md)** - Deployment patterns and methodologies -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and management +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and management --- @@ -584,10 +584,10 @@ resource "datadog_dashboard" "deployment_monitoring" { ## 🔗 Related Practices -- **[Operations Monitoring](.pair/knowledge/guidelines/observability/README.md)** - General application and infrastructure monitoring -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Operations Monitoring](../../observability/README.md)** - General application and infrastructure monitoring +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices - **[Deployment Strategies](deployment-strategies.md)** - Deployment patterns and methodologies -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and management +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and management --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/performance.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/performance.md index ff93e500..865b50d6 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/performance.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/performance.md @@ -662,8 +662,8 @@ interface DeploymentPerformanceSLIs { ## 🔗 Related Practices -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and management +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and management - **[Deployment Strategies](deployment-strategies.md)** - Deployment patterns and methodologies - **[Monitoring](monitoring.md)** - Deployment monitoring and observability diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/security.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/security.md index 89b3d3b1..620f9fc3 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/security.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/deployment-patterns/security.md @@ -434,10 +434,10 @@ class ComplianceValidator { ## 🔗 Related Practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Secure infrastructure automation -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Secure pipeline implementation +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Secure infrastructure automation +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Secure pipeline implementation - **[Deployment Strategies](deployment-strategies.md)** - Secure deployment patterns -- **[Security Operations](.pair/knowledge/guidelines/quality-assurance/security/README.md)** - General security operations and monitoring +- **[Security Operations](../../quality-assurance/security/README.md)** - General security operations and monitoring --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/README.md index 39f426f0..c0ad3508 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/README.md @@ -231,10 +231,10 @@ Setting up environment management? ## 🔗 Related Practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control -- **[Deployment Patterns](.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md)** - Application deployment strategies and automation -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud service selection and integration +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[Deployment Patterns](../deployment-patterns/README.md)** - Application deployment strategies and automation +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Cloud Services](../cloud-services/README.md)** - Cloud service selection and integration ## 📈 Environment Management Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/environment-consistency.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/environment-consistency.md index 2541a008..ddba8d9d 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/environment-consistency.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/environment-consistency.md @@ -311,10 +311,10 @@ echo "✅ Environment consistency validation completed" ## 🔗 Related Practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure standardization and automation +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure standardization and automation - **[Environment Configuration](environment-config.md)** - Configuration management and templating -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Deployment pipeline consistency -- **[Monitoring and Observability](.pair/knowledge/guidelines/observability/README.md)** - Environment monitoring and alerting +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Deployment pipeline consistency +- **[Monitoring and Observability](../../observability/README.md)** - Environment monitoring and alerting --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/local-development.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/local-development.md index 8b79242c..b0e10dcb 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/local-development.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/local-development.md @@ -560,8 +560,8 @@ development_security: - **[Environment Consistency](environment-consistency.md)** - Maintaining consistency across environments - **[Environment Configuration](environment-config.md)** - Configuration management strategies -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Development workflow integration -- **[Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md)** - Local testing approaches and frameworks +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Development workflow integration +- **[Testing Strategy](../../testing/test-strategy/README.md)** - Local testing approaches and frameworks --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/production-development.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/production-development.md index fe6a6d5d..b40ff002 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/production-development.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/production-development.md @@ -210,8 +210,8 @@ Production monitoring richiede end-to-end visibility across all system component - **[Staging Development](staging-development.md)** - Pre-production validation environment - **[Environment Configuration](environment-config.md)** - Environment configuration management -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and management -- **[Operations Monitoring](.pair/knowledge/guidelines/observability/README.md)** - Production monitoring and observability +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and management +- **[Operations Monitoring](../../observability/README.md)** - Production monitoring and observability --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/service-discovery.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/service-discovery.md index ed9f628b..b31a47b4 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/service-discovery.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/service-discovery.md @@ -210,10 +210,10 @@ Il service mesh fornisce sophisticated discovery con security e observability: ## 🔗 Related Practices -- **[Container Orchestration](.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md)** - Container-based service discovery +- **[Container Orchestration](../container-orchestration/README.md)** - Container-based service discovery - **[Environment Management](README.md)** - Environment-specific discovery strategies -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud-native discovery services -- **[API Management](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - API discovery and routing patterns +- **[Cloud Services](../cloud-services/README.md)** - Cloud-native discovery services +- **[API Management](../cloud-services/README.md)** - API discovery and routing patterns --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/staging-development.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/staging-development.md index 956b0e0c..d857ef5d 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/staging-development.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/environments/staging-development.md @@ -197,7 +197,7 @@ Lo staging environment deve validate performance characteristics prima del produ - **[Production Environment](production-development.md)** - Production environment management strategies - **[Local Development](local-development.md)** - Development environment setup and consistency - **[Environment Configuration](environment-config.md)** - Environment configuration management -- **[Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md)** - Comprehensive testing methodologies +- **[Testing Strategy](../../testing/test-strategy/README.md)** - Comprehensive testing methodologies --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md index d4124ace..ddb7726a 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md @@ -162,10 +162,10 @@ Do you need infrastructure automation? ## 🔗 Related Practices -- **[Cloud Providers](.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md)** - Cloud platform selection and implementation -- **[Container Orchestration](.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md)** - Container infrastructure automation -- **[Deployment Patterns](.pair/knowledge/guidelines/infrastructure/deployment-patterns/README.md)** - Infrastructure deployment strategies -- **[Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md)** - Infrastructure security practices +- **[Cloud Providers](../cloud-providers/README.md)** - Cloud platform selection and implementation +- **[Container Orchestration](../container-orchestration/README.md)** - Container infrastructure automation +- **[Deployment Patterns](../deployment-patterns/README.md)** - Infrastructure deployment strategies +- **[Security Guidelines](../../quality-assurance/security/README.md)** - Infrastructure security practices ## 🎓 Learning Path diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/automation.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/automation.md index 87ef6e18..a6fb9775 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/automation.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/automation.md @@ -223,8 +223,8 @@ Self-healing infrastructure identifica e risolve automaticamente problemi comuni - **[IaC Best Practices](iac-best-practices.md)** - Infrastructure as Code implementation guidelines - **[State Management](state-management.md)** - Infrastructure state management strategies -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Operations Monitoring](.pair/knowledge/guidelines/observability/README.md)** - Infrastructure monitoring and observability +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Operations Monitoring](../../observability/README.md)** - Infrastructure monitoring and observability --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/aws-cdk-implementation.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/aws-cdk-implementation.md index 4a0a9311..a615563d 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/aws-cdk-implementation.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/aws-cdk-implementation.md @@ -260,7 +260,7 @@ test('Database has encryption enabled', () => { - **[IaC Best Practices](iac-best-practices.md)** - Infrastructure as Code best practices - **[Terraform Implementation](terraform.md)** - Terraform-specific patterns -- **[AWS Deployment](.pair/knowledge/guidelines/infrastructure/cloud-providers/aws-deployment.md)** - AWS-specific deployment strategies +- **[AWS Deployment](../cloud-providers/aws-deployment.md)** - AWS-specific deployment strategies - **[Automation](automation.md)** - Infrastructure automation frameworks --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/operational-excellence.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/operational-excellence.md index ae22b912..50ff3735 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/operational-excellence.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/operational-excellence.md @@ -228,8 +228,8 @@ La capacity management deve essere proactive utilizzando historical data e predi - **[Infrastructure Automation](automation.md)** - Infrastructure automation strategies and implementation - **[IaC Best Practices](iac-best-practices.md)** - Infrastructure as Code excellence practices -- **[Operations Monitoring](.pair/knowledge/guidelines/observability/README.md)** - Comprehensive monitoring strategies -- **[Incident Management](.pair/knowledge/guidelines/observability/README.md)** - Incident response and management +- **[Operations Monitoring](../../observability/README.md)** - Comprehensive monitoring strategies +- **[Incident Management](../../observability/README.md)** - Incident response and management --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/README.md index affa07ec..13ee8111 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/README.md @@ -281,10 +281,10 @@ Testing Environment Tiers: ## 🔗 Related Practices -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Environments](.pair/knowledge/guidelines/infrastructure/environments/README.md)** - Environment management and consistency strategies -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and version control -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud service selection and integration +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Environments](../environments/README.md)** - Environment management and consistency strategies +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and version control +- **[Cloud Services](../cloud-services/README.md)** - Cloud service selection and integration ## 📈 Testing Infrastructure Maturity Progression diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/performance-testing.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/performance-testing.md index 5eb21553..631a6526 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/performance-testing.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/performance-testing.md @@ -331,10 +331,10 @@ class PerformanceReportGenerator: ## 🔗 Related Practices -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - Continuous integration and deployment practices -- **[Monitoring and Observability](.pair/knowledge/guidelines/observability/README.md)** - Production monitoring and observability -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud service performance optimization -- **[Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md)** - Overall testing methodology and approach +- **[CI/CD Strategy](../cicd-strategy/README.md)** - Continuous integration and deployment practices +- **[Monitoring and Observability](../../observability/README.md)** - Production monitoring and observability +- **[Cloud Services](../cloud-services/README.md)** - Cloud service performance optimization +- **[Testing Strategy](../../testing/test-strategy/README.md)** - Overall testing methodology and approach --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-databases.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-databases.md index 014de288..73f743d8 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-databases.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-databases.md @@ -212,8 +212,8 @@ L'automazione del database testing garantisce consistency e efficiency: - **[Test Environments](test-environments.md)** - Test environment management and provisioning - **[Performance Testing](performance-testing.md)** - Performance testing infrastructure and methodologies -- **[Data Management](.pair/knowledge/guidelines/infrastructure/README.md)** - Enterprise data management strategies -- **[Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md)** - Data security and privacy frameworks +- **[Data Management](../README.md)** - Enterprise data management strategies +- **[Security Guidelines](../../quality-assurance/security/README.md)** - Data security and privacy frameworks --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-environments.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-environments.md index 88cce55e..1dd5339e 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-environments.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/infrastructure/testing-infrastructure/test-environments.md @@ -171,10 +171,10 @@ La gestione dei test data richiede strategie sofisticate per garantire data cons ## 🔗 Related Practices -- **[Infrastructure as Code](.pair/knowledge/guidelines/infrastructure/infrastructure-as-code/README.md)** - Infrastructure automation and provisioning +- **[Infrastructure as Code](../infrastructure-as-code/README.md)** - Infrastructure automation and provisioning - **[Performance Testing](performance-testing.md)** - Performance testing infrastructure requirements - **[Test Databases](test-databases.md)** - Database testing and data management strategies -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Cloud service utilization for testing environments +- **[Cloud Services](../cloud-services/README.md)** - Cloud service utilization for testing environments --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/README.md index 12d97990..13ccc5b1 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/README.md @@ -160,7 +160,7 @@ Do you need enterprise support and budget allows? ## Related Documents -- [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) - Infrastructure monitoring requirements -- [Definition of Done](.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md) - Observability requirements -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) - Test environment monitoring -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) - Security monitoring requirements +- [Infrastructure Guidelines](../infrastructure/README.md) - Infrastructure monitoring requirements +- [Definition of Done](../quality-assurance/quality-standards/definition-of-done.md) - Observability requirements +- [Testing Strategy](../testing/README.md) - Test environment monitoring +- [Security Guidelines](../quality-assurance/security/README.md) - Security monitoring requirements diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/README.md index 15a23dc6..f203cfe6 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/README.md @@ -259,7 +259,7 @@ Start: What's your team size and complexity? ## Related Documents -- [Observability Tools](.pair/knowledge/guidelines/observability/observability-tools.md) - Alert tool selection and implementation -- [Proactive Detection](.pair/knowledge/guidelines/observability/proactive-detection.md) - Early warning system design -- [Performance Analysis](.pair/knowledge/guidelines/observability/performance-analysis.md) - Performance-based alerting -- [Metrics Strategy](.pair/knowledge/guidelines/observability/metrics/README.md) - Metrics for alerting +- [Observability Tools](../observability-tools.md) - Alert tool selection and implementation +- [Proactive Detection](../proactive-detection.md) - Early warning system design +- [Performance Analysis](../performance-analysis.md) - Performance-based alerting +- [Metrics Strategy](../metrics/README.md) - Metrics for alerting diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/notifications.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/notifications.md index 139e25d5..0ba0206f 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/notifications.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/notifications.md @@ -407,5 +407,5 @@ Effective notification strategies ensure that critical information reaches the r ## Related Documents - [Alerting Strategy](strategy.md) - Alert design and optimization principles -- [Observability Tools](.pair/knowledge/guidelines/observability/observability-tools.md) - Tool selection for notifications -- [Workflow Integration](.pair/knowledge/guidelines/observability/workflow-integration.md) - Process integration strategies +- [Observability Tools](../observability-tools.md) - Tool selection for notifications +- [Workflow Integration](../workflow-integration.md) - Process integration strategies diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/strategy.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/strategy.md index 5a303d93..82daf8f9 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/strategy.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/alerting/strategy.md @@ -408,6 +408,6 @@ A well-designed alerting strategy balances sensitivity with specificity, ensurin ## Related Documents - [Notifications](notifications.md) - Notification channel and delivery strategies -- [Proactive Detection](.pair/knowledge/guidelines/observability/proactive-detection.md) - Predictive monitoring approaches -- [AI-Enhanced Observability](.pair/knowledge/guidelines/observability/ai-enhanced-observability.md) - Machine learning integration -- [Performance Analysis](.pair/knowledge/guidelines/observability/performance-analysis.md) - Performance-based alerting +- [Proactive Detection](../proactive-detection.md) - Predictive monitoring approaches +- [AI-Enhanced Observability](../ai-enhanced-observability.md) - Machine learning integration +- [Performance Analysis](../performance-analysis.md) - Performance-based alerting diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/metrics/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/metrics/README.md index 06370ee8..2be9b758 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/metrics/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/metrics/README.md @@ -303,7 +303,7 @@ Start: What's your primary use case? ## Related Documents -- [Performance Analysis](.pair/knowledge/guidelines/observability/performance-analysis.md) - Performance metrics analysis techniques -- [Dashboards and Visualization](.pair/knowledge/guidelines/observability/dashboards-visualization.md) - Metrics visualization strategies -- [Alerting Strategy](.pair/knowledge/guidelines/observability/alerting/README.md) - Metrics-based alerting -- [Observability Tools](.pair/knowledge/guidelines/observability/observability-tools.md) - Tool selection and implementation +- [Performance Analysis](../performance-analysis.md) - Performance metrics analysis techniques +- [Dashboards and Visualization](../dashboards-visualization.md) - Metrics visualization strategies +- [Alerting Strategy](../alerting/README.md) - Metrics-based alerting +- [Observability Tools](../observability-tools.md) - Tool selection and implementation diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/README.md index d56ada6d..26881703 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/README.md @@ -98,7 +98,7 @@ Observability principles provide the foundational framework for building effecti ## Related Documents -- [Metrics Strategy](.pair/knowledge/guidelines/observability/metrics/README.md) - Metrics implementation guidance -- [Structured Logging](.pair/knowledge/guidelines/observability/structured-logging/README.md) - Logging best practices -- [Distributed Tracing](.pair/knowledge/guidelines/observability/distributed-tracing.md) - Tracing implementation -- [AI-Enhanced Observability](.pair/knowledge/guidelines/observability/ai-enhanced-observability.md) - Advanced observability techniques +- [Metrics Strategy](../metrics/README.md) - Metrics implementation guidance +- [Structured Logging](../structured-logging/README.md) - Logging best practices +- [Distributed Tracing](../distributed-tracing.md) - Tracing implementation +- [AI-Enhanced Observability](../ai-enhanced-observability.md) - Advanced observability techniques diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/proactive-monitoring.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/proactive-monitoring.md index 4141c40d..b5563255 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/proactive-monitoring.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/proactive-monitoring.md @@ -111,6 +111,6 @@ Define proactive monitoring strategies that enable early problem detection and p ## Related Documents - [Three Pillars](three-pillars.md) - Foundational observability concepts -- [Proactive Detection](.pair/knowledge/guidelines/observability/proactive-detection.md) - Detailed proactive detection strategies -- [AI-Enhanced Observability](.pair/knowledge/guidelines/observability/ai-enhanced-observability.md) - AI-powered proactive monitoring -- [Performance Analysis](.pair/knowledge/guidelines/observability/performance-analysis.md) - Performance trend analysis +- [Proactive Detection](../proactive-detection.md) - Detailed proactive detection strategies +- [AI-Enhanced Observability](../ai-enhanced-observability.md) - AI-powered proactive monitoring +- [Performance Analysis](../performance-analysis.md) - Performance trend analysis diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/three-pillars.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/three-pillars.md index b2cb200a..67e5e286 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/three-pillars.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/observability-principles/three-pillars.md @@ -97,6 +97,6 @@ Define the foundational three pillars of observability (metrics, logs, traces) a ## Related Documents - [Proactive Monitoring](proactive-monitoring.md) - Proactive monitoring strategies -- [Metrics Strategy](.pair/knowledge/guidelines/observability/metrics/README.md) - Detailed metrics guidance -- [Structured Logging](.pair/knowledge/guidelines/observability/structured-logging/README.md) - Logging implementation -- [Distributed Tracing](.pair/knowledge/guidelines/observability/distributed-tracing.md) - Tracing strategies +- [Metrics Strategy](../metrics/README.md) - Detailed metrics guidance +- [Structured Logging](../structured-logging/README.md) - Logging implementation +- [Distributed Tracing](../distributed-tracing.md) - Tracing strategies diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/structured-logging/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/structured-logging/README.md index 86390eb5..b9de6a09 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/structured-logging/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/observability/structured-logging/README.md @@ -123,7 +123,7 @@ Start: What's your primary use case? ## Related Documents -- [Observability Principles](.pair/knowledge/guidelines/observability/observability-principles/README.md) - Core observability concepts -- [Performance Analysis](.pair/knowledge/guidelines/observability/performance-analysis.md) - Log analysis for performance -- [AI-Enhanced Observability](.pair/knowledge/guidelines/observability/ai-enhanced-observability.md) - AI-powered log analysis -- [Workflow Integration](.pair/knowledge/guidelines/observability/workflow-integration.md) - Logging in development workflows +- [Observability Principles](../observability-principles/README.md) - Core observability concepts +- [Performance Analysis](../performance-analysis.md) - Log analysis for performance +- [AI-Enhanced Observability](../ai-enhanced-observability.md) - AI-powered log analysis +- [Workflow Integration](../workflow-integration.md) - Logging in development workflows diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/accessibility/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/accessibility/README.md index c9931326..465e470a 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/accessibility/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/accessibility/README.md @@ -254,9 +254,9 @@ Start → Team Size? ## Cross-References -- **Development**: [code-design/quality-standards/](.pair/knowledge/guidelines/code-design/quality-standards) - Accessibility in code quality -- **Testing**: [testing/testing-strategy/](.pair/knowledge/guidelines/testing/test-strategy) - Accessibility testing integration -- **UX Design**: [operations/ux-design/](.pair/knowledge/guidelines/user-experience/README.md) - Inclusive design principles +- **Development**: [code-design/quality-standards/](../../code-design/quality-standards) - Accessibility in code quality +- **Testing**: [testing/testing-strategy/](../../testing/test-strategy) - Accessibility testing integration +- **UX Design**: [operations/ux-design/](../../user-experience/README.md) - Inclusive design principles ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/optimization-strategies.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/optimization-strategies.md index 7b7a2b4d..89605b51 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/optimization-strategies.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/optimization-strategies.md @@ -335,8 +335,8 @@ Provide actionable optimization strategies and techniques that development teams - **[Performance Fundamentals](performance-fundamentals.md)** - Core performance concepts and principles - **[Core Web Vitals](core-web-vitals.md)** - Google Core Web Vitals specific optimization -- **[Testing Guidelines](.pair/knowledge/guidelines/testing/README.md)** - Performance testing and validation -- **[Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md)** - Infrastructure-level performance optimization +- **[Testing Guidelines](../../testing/README.md)** - Performance testing and validation +- **[Infrastructure Guidelines](../../infrastructure/README.md)** - Infrastructure-level performance optimization --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/performance-fundamentals.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/performance-fundamentals.md index 87846b88..24d5fdd0 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/performance-fundamentals.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/performance/performance-fundamentals.md @@ -326,8 +326,8 @@ Establish foundational performance knowledge and principles that guide the devel - **[Core Web Vitals](core-web-vitals.md)** - Specific Google Core Web Vitals optimization - **[Optimization Strategies](optimization-strategies.md)** - Practical optimization techniques -- **[Testing Guidelines](.pair/knowledge/guidelines/testing/README.md)** - Performance testing integration -- **[Observability Guidelines](.pair/knowledge/guidelines/observability/README.md)** - Performance monitoring and metrics +- **[Testing Guidelines](../../testing/README.md)** - Performance testing integration +- **[Observability Guidelines](../../observability/README.md)** - Performance monitoring and metrics --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-monitoring/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-monitoring/README.md index 31a38498..8eaf6c30 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-monitoring/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-monitoring/README.md @@ -30,21 +30,21 @@ Comprehensive quality monitoring framework ensuring continuous quality assessmen ### **Related Quality Standards** -- **[Quality Gates Framework](.pair/knowledge/guidelines/quality-assurance/quality-standards/quality-gates.md)** ✅ - Strategic quality checkpoints and validation processes -- **[Quality Improvement Process](.pair/knowledge/guidelines/quality-assurance/quality-standards/improvement-process.md)** ✅ - Systematic continuous improvement framework -- **[Verification Methods](.pair/knowledge/guidelines/quality-assurance/quality-standards/verification-methods.md)** ✅ - Comprehensive quality verification approaches +- **[Quality Gates Framework](../quality-standards/quality-gates.md)** ✅ - Strategic quality checkpoints and validation processes +- **[Quality Improvement Process](../quality-standards/improvement-process.md)** ✅ - Systematic continuous improvement framework +- **[Verification Methods](../quality-standards/verification-methods.md)** ✅ - Comprehensive quality verification approaches ### **Related Security Monitoring** -- **[Security Testing Framework](.pair/knowledge/guidelines/quality-assurance/security/security-testing.md)** ✅ - Comprehensive security testing methodology -- **[SAST Static Testing](.pair/knowledge/guidelines/quality-assurance/security/sast-static-testing.md)** ✅ - Static application security testing framework -- **[Security Quality Gates](.pair/knowledge/guidelines/quality-assurance/security/security-quality-gates.md)** ✅ - Security checkpoints and validation processes +- **[Security Testing Framework](../security/security-testing.md)** ✅ - Comprehensive security testing methodology +- **[SAST Static Testing](../security/sast-static-testing.md)** ✅ - Static application security testing framework +- **[Security Quality Gates](../security/security-quality-gates.md)** ✅ - Security checkpoints and validation processes ### **Related Performance Standards** -- **[Core Web Vitals](.pair/knowledge/guidelines/quality-assurance/performance/core-web-vitals.md)** ✅ - Essential web performance metrics -- **[Performance Monitoring](.pair/knowledge/guidelines/quality-assurance/performance/monitoring.md)** ✅ - Comprehensive performance monitoring framework -- **[Performance Testing Strategies](.pair/knowledge/guidelines/quality-assurance/performance/testing-strategies.md)** ✅ - Performance testing methodologies +- **[Core Web Vitals](../performance/core-web-vitals.md)** ✅ - Essential web performance metrics +- **[Performance Monitoring](../performance/monitoring.md)** ✅ - Comprehensive performance monitoring framework +- **[Performance Testing Strategies](../performance/testing-strategies.md)** ✅ - Performance testing methodologies ## 🔧 **QUALITY MONITORING TOOLS COMPARISON** diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md index c98c2ff1..9dab39a9 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md @@ -83,9 +83,9 @@ Start → Team Size? ## 🔗 Related Practices -- **[Testing](.pair/knowledge/guidelines/testing)** - Testing requirements within quality standards -- **[Accessibility](.pair/knowledge/guidelines/quality-assurance/accessibility)** - Accessibility compliance as quality requirement -- **[Security](.pair/knowledge/guidelines/quality-assurance/security)** - Security standards integrated with quality criteria +- **[Testing](../../testing)** - Testing requirements within quality standards +- **[Accessibility](../accessibility)** - Accessibility compliance as quality requirement +- **[Security](../security)** - Security standards integrated with quality criteria --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md index d368fb89..f7b04016 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md @@ -55,21 +55,21 @@ Ensure consistent quality across all deliverables in the development process, pr Complete checklist ordered by priority for each work item: - [ ] Requirements implemented and acceptance criteria met -- [ ] Code follows [Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md) -- [ ] Tech guidance followed per [Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md) -- [ ] Technical approach aligns with [Architectural Guidelines](.pair/knowledge/guidelines/architecture/README.md) -- [ ] ADRs (Architectural Decision Records) followed per [Architectural Guidelines](.pair/knowledge/guidelines/architecture/README.md) -- [ ] Tests written per [Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) -- [ ] All automated tests passing per [Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) +- [ ] Code follows [Code Design Guidelines](../../code-design/README.md) +- [ ] Tech guidance followed per [Technical Guidelines](../../technical-standards/README.md) +- [ ] Technical approach aligns with [Architectural Guidelines](../../architecture/README.md) +- [ ] ADRs (Architectural Decision Records) followed per [Architectural Guidelines](../../architecture/README.md) +- [ ] Tests written per [Testing Strategy](../../testing/test-strategy/README.md) +- [ ] All automated tests passing per [Testing Strategy](../../testing/test-strategy/README.md) - [ ] Code review completed and approved - [ ] Security considerations identified, practices followed, and scanning passed per [Security Guidelines]../security/security-guidelines.md - [ ] Performance benchmarks met per [Performance Guidelines]../performance/performance-guidelines.md -- [ ] Quality gates passed per [Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md) +- [ ] Quality gates passed per [Technical Guidelines](../../technical-standards/README.md) - [ ] Accessibility criteria met per [Accessibility Guidelines]../accessibility/accessibility-guidelines.md -- [ ] UX criteria met per [UX Guidelines](.pair/knowledge/guidelines/user-experience/README.md) +- [ ] UX criteria met per [UX Guidelines](../../user-experience/README.md) - [ ] Feature under feature flag (if applicable) -- [ ] IaaS implemented per [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) -- [ ] Monitoring configured per [Observability Guidelines](.pair/knowledge/guidelines/observability/README.md) +- [ ] IaaS implemented per [Infrastructure Guidelines](../../infrastructure/README.md) +- [ ] Monitoring configured per [Observability Guidelines](../../observability/README.md) - [ ] Deployment successful - [ ] Documentation updated and published @@ -79,17 +79,17 @@ Complete checklist ordered by priority for each work item: | Criteria | Primary Responsibility | Tool Assistance | Guidelines Reference | | ------------------------- | ---------------------- | --------------- | ------------------------------------------------------------------------------------------- | -| Requirements & Acceptance | Team Review | High | [Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md) | -| Technical Standards | Team Review | High | [Architectural Guidelines](.pair/knowledge/guidelines/architecture/README.md) | -| ADRs Compliance | Team Review | Medium | [Architectural Guidelines](.pair/knowledge/guidelines/architecture/README.md) | -| Tech Guidance | Team Review | High | [Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md) | -| Infrastructure | DevOps Team | Medium | [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) | -| UX Criteria | UX/Dev Team | Medium | [UX Guidelines](.pair/knowledge/guidelines/user-experience/README.md) | +| Requirements & Acceptance | Team Review | High | [Code Design Guidelines](../../code-design/README.md) | +| Technical Standards | Team Review | High | [Architectural Guidelines](../../architecture/README.md) | +| ADRs Compliance | Team Review | Medium | [Architectural Guidelines](../../architecture/README.md) | +| Tech Guidance | Team Review | High | [Technical Guidelines](../../technical-standards/README.md) | +| Infrastructure | DevOps Team | Medium | [Infrastructure Guidelines](../../infrastructure/README.md) | +| UX Criteria | UX/Dev Team | Medium | [UX Guidelines](../../user-experience/README.md) | | Accessibility | UX/Dev Team | Medium | [Accessibility Guidelines]../accessibility/accessibility-guidelines.md | | Security Assessment | Security Lead | Medium | [Security Guidelines]../security/security-guidelines.md | | Performance | Dev Team | High | [Performance Guidelines]../performance/performance-guidelines.md | -| Testing Strategy | Dev Team | High | [Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) | -| Observability | Dev Team | High | [Observability Guidelines](.pair/knowledge/guidelines/observability/README.md) | +| Testing Strategy | Dev Team | High | [Testing Strategy](../../testing/test-strategy/README.md) | +| Observability | Dev Team | High | [Observability Guidelines](../../observability/README.md) | --- @@ -163,8 +163,8 @@ All work items must satisfy these criteria before being considered complete. Ref ### 📋 Requirements & Technical Standards - **Acceptance Criteria Met** → All story/task requirements satisfied -- **Architecture Compliance** → Solution aligns with [Architectural Guidelines](.pair/knowledge/guidelines/architecture/README.md) -- **Code Standards** → Code follows [Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md) and [Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md) +- **Architecture Compliance** → Solution aligns with [Architectural Guidelines](../../architecture/README.md) +- **Code Standards** → Code follows [Code Design Guidelines](../../code-design/README.md) and [Technical Guidelines](../../technical-standards/README.md) - **Code Review Completed** → Human review conducted with AI assistance ### 🔒 Security Assessment @@ -187,13 +187,13 @@ All work items must satisfy these criteria before being considered complete. Ref ### 🧪 Testing Requirements -- **Test Coverage** → Standards met per [Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) +- **Test Coverage** → Standards met per [Testing Strategy](../../testing/test-strategy/README.md) - **Test Quality** → Meaningful tests verifying behavior, not implementation - **Automated Tests** → All CI/CD pipeline tests passing ### � Operational Readiness -- **Monitoring** → Health checks and observability per [Observability Guidelines](.pair/knowledge/guidelines/observability/README.md) +- **Monitoring** → Health checks and observability per [Observability Guidelines](../../observability/README.md) - **Documentation** → Technical and deployment documentation updated - **Deployment** → Environment compatibility and rollback strategy tested @@ -206,7 +206,7 @@ Automated quality gates integrated in CI/CD pipeline: ### 📊 Code Quality - **Static Analysis** → SonarQube/ESLint A rating or higher -- **Technical Debt** → Standards met per [Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md) +- **Technical Debt** → Standards met per [Technical Guidelines](../../technical-standards/README.md) - **Security** → SAST passed, no secrets detected ### ⚡ Performance @@ -219,7 +219,7 @@ Automated quality gates integrated in CI/CD pipeline: ## 📈 Observability & Monitoring -Operational readiness requires robust observability practices to ensure system health, reliability, and rapid incident response. All deliverables must comply with the following observability requirements, aligned with [Observability Guidelines](.pair/knowledge/guidelines/observability/README.md): +Operational readiness requires robust observability practices to ensure system health, reliability, and rapid incident response. All deliverables must comply with the following observability requirements, aligned with [Observability Guidelines](../../observability/README.md): ### Monitoring Requirements @@ -250,7 +250,7 @@ Operational readiness requires robust observability practices to ensure system h - **Readiness & Liveness Probes:** Implement readiness and liveness probes for containerized workloads. - **Monitoring Integration:** Health check endpoints must be integrated with monitoring systems for automated status tracking. -Refer to [Observability Guidelines](.pair/knowledge/guidelines/observability/README.md) for detailed implementation instructions. +Refer to [Observability Guidelines](../../observability/README.md) for detailed implementation instructions. ## 🔍 Verification Process @@ -288,18 +288,18 @@ This Definition of Done serves as the **central quality framework** that ensures **Core Technical Standards:** -- **[Architectural Guidelines](.pair/knowledge/guidelines/architecture/README.md)** - _Architecture standards define quality baseline_ -- **[Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md)** - _Code standards verified in checklist_ -- **[Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md)** - _Tech compliance must be validated_ -- **[Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md)** - _Deployment readiness ensures production quality_ +- **[Architectural Guidelines](../../architecture/README.md)** - _Architecture standards define quality baseline_ +- **[Code Design Guidelines](../../code-design/README.md)** - _Code standards verified in checklist_ +- **[Technical Guidelines](../../technical-standards/README.md)** - _Tech compliance must be validated_ +- **[Infrastructure Guidelines](../../infrastructure/README.md)** - _Deployment readiness ensures production quality_ **Quality & User Experience:** -- **[UX Guidelines](.pair/knowledge/guidelines/user-experience/README.md)** - _UX standards ensure user-facing quality_ -- **[Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md)** - _Testing validates feature completeness_ +- **[UX Guidelines](../../user-experience/README.md)** - _UX standards ensure user-facing quality_ +- **[Testing Strategy](../../testing/test-strategy/README.md)** - _Testing validates feature completeness_ **Collaboration & Process:** -- **[project-management/README.md](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md)** - _Collaboration and process standards_ +- **[project-management/README.md](../../collaboration/project-management-tool/README.md)** - _Collaboration and process standards_ This Definition of Done provides a clear, verifiable framework that ensures consistent quality while leveraging the detailed guidance in specialized technical documents. diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/README.md index 727caec5..3896f53f 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/README.md @@ -375,9 +375,9 @@ Security testing and vulnerability assessment ## Cross-References -- **Development**: [code-design/quality-standards/](.pair/knowledge/guidelines/code-design/quality-standards) - Secure coding standards -- **Operations**: [operations/infrastructure.md](.pair/knowledge/guidelines/infrastructure/README.md) - Infrastructure security implementation -- **Testing**: [testing/testing-strategy/](.pair/knowledge/guidelines/testing/test-strategy) - Security testing integration +- **Development**: [code-design/quality-standards/](../../code-design/quality-standards) - Secure coding standards +- **Operations**: [operations/infrastructure.md](../../infrastructure/README.md) - Infrastructure security implementation +- **Testing**: [testing/testing-strategy/](../../testing/test-strategy) - Security testing integration ## Scope Boundaries diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/authentication-authorization.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/authentication-authorization.md index e502d637..24d38204 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/authentication-authorization.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/authentication-authorization.md @@ -325,7 +325,7 @@ Establish robust authentication and authorization standards that ensure secure u - **[Security Guidelines](security-guidelines.md)** - Comprehensive security standards and frameworks - **[Security by Design](security-by-design.md)** - Proactive security integration in development - **[API Security](api-security.md)** - API-specific security patterns and controls -- **[Infrastructure Security](.pair/knowledge/guidelines/infrastructure/README.md)** - Infrastructure-level security controls +- **[Infrastructure Security](../../infrastructure/README.md)** - Infrastructure-level security controls --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/security-by-design.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/security-by-design.md index fbcb74b1..1803283d 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/security-by-design.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/quality-assurance/security/security-by-design.md @@ -363,9 +363,9 @@ Establish security by design principles that embed security considerations into ## 🔗 Related Practices - **[Security Guidelines](security-guidelines.md)** - Comprehensive security standards and practices -- **[Testing Guidelines](.pair/knowledge/guidelines/testing/README.md)** - Security testing integration and methodologies -- **[Quality Standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md)** - Quality assurance and validation processes -- **[Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md)** - Secure coding practices and standards +- **[Testing Guidelines](../../testing/README.md)** - Security testing integration and methodologies +- **[Quality Standards](../quality-standards/README.md)** - Quality assurance and validation processes +- **[Code Design Guidelines](../../code-design/README.md)** - Secure coding practices and standards --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/ai-tools.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/ai-tools.md index e55f2034..5db088b1 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/ai-tools.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/ai-tools.md @@ -831,6 +831,6 @@ export class MonitoredAIService implements AIService { - [Documentation Standards](documentation-standards.md) - [MCP Integration](mcp-integration.md) -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- [Performance Guidelines](.pair/knowledge/guidelines/observability/README.md) -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) +- [Security Guidelines](../../quality-assurance/security/README.md) +- [Performance Guidelines](../../observability/README.md) +- [Testing Strategy](../../testing/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/documentation-standards.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/documentation-standards.md index 20b35657..cb8d7f23 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/documentation-standards.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/documentation-standards.md @@ -498,6 +498,6 @@ export class PrivacyAwareAIService { - [AI Tools Integration](ai-tools.md) - [MCP Integration Standards](mcp-integration.md) -- [Technical Guidelines](.pair/knowledge/guidelines/technical-standards/README.md) -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) +- [Technical Guidelines](../README.md) +- [Security Guidelines](../../quality-assurance/security/README.md) +- [Testing Strategy](../../testing/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/mcp-integration.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/mcp-integration.md index 811f46e8..814a67f4 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/mcp-integration.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/ai-development/mcp-integration.md @@ -945,6 +945,6 @@ export class MonitoredMCPServer extends DynamicMCPServer { - [AI Development Tools](ai-tools.md) - [Documentation Standards](documentation-standards.md) -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- [Performance Guidelines](.pair/knowledge/guidelines/observability/README.md) -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) +- [Security Guidelines](../../quality-assurance/security/README.md) +- [Performance Guidelines](../../observability/README.md) +- [Testing Strategy](../../testing/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/coding-standards/i18n-localization.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/coding-standards/i18n-localization.md index f4eca878..49ca05ab 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/coding-standards/i18n-localization.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/coding-standards/i18n-localization.md @@ -546,7 +546,7 @@ export class LocaleDetectionService { ## Related Documentation -- [User Experience Guidelines](.pair/knowledge/guidelines/user-experience/README.md) -- [Accessibility Standards](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md) -- [Content Strategy](.pair/knowledge/guidelines/user-experience/content-strategy/README.md) -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) +- [User Experience Guidelines](../../user-experience/README.md) +- [Accessibility Standards](../../quality-assurance/accessibility/README.md) +- [Content Strategy](../../user-experience/content-strategy/README.md) +- [Testing Strategy](../../testing/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/deployment-workflow/build-standards.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/deployment-workflow/build-standards.md index 9673fd3a..ebfad2a3 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/deployment-workflow/build-standards.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/deployment-workflow/build-standards.md @@ -1109,6 +1109,6 @@ export class BuildArtifactSecurityValidator { - [Deployment Automation](deployment-automation.md) - [Release Management](release-management.md) - [Strategy Guidelines](strategy.md) -- [Quality Assurance](.pair/knowledge/guidelines/quality-assurance/README.md) -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- [Performance Guidelines](.pair/knowledge/guidelines/observability/README.md) +- [Quality Assurance](../../quality-assurance/README.md) +- [Security Guidelines](../../quality-assurance/security/README.md) +- [Performance Guidelines](../../observability/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/development-tools/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/development-tools/README.md index 8649c65c..400526c1 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/development-tools/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/development-tools/README.md @@ -424,9 +424,9 @@ This section covers development environment and tooling standards: ## 🔗 Related Practices -- **[Technology Stack](.pair/knowledge/guidelines/technical-standards/technology-stack/README.md)** - Technology choices that these tools support -- **[Coding Standards](.pair/knowledge/guidelines/technical-standards/coding-standards/README.md)** - Development environment patterns -- **[Deployment Workflow](.pair/knowledge/guidelines/technical-standards/deployment-workflow/README.md)** - Tools that support build and deployment +- **[Technology Stack](../technology-stack/README.md)** - Technology choices that these tools support +- **[Coding Standards](../coding-standards/README.md)** - Development environment patterns +- **[Deployment Workflow](../deployment-workflow/README.md)** - Tools that support build and deployment ## 🎯 Quick Start diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/feature-flags.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/feature-flags.md index 42b621d5..5a7af5fd 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/feature-flags.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/feature-flags.md @@ -304,5 +304,5 @@ export class FlagCleanupService { - [Technical Debt Management](coding-standards/technical-debt.md) - [Deployment Workflow](deployment-workflow/README.md) -- [Quality Assurance Standards](.pair/knowledge/guidelines/quality-assurance/README.md) -- [Observability Guidelines](.pair/knowledge/guidelines/observability/README.md) +- [Quality Assurance Standards](../quality-assurance/README.md) +- [Observability Guidelines](../observability/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/development-process.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/development-process.md index 7653bf4e..793b761a 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/development-process.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/development-process.md @@ -547,6 +547,6 @@ jobs: - [Version Control Standards](version-control.md) - [Quality Assurance Process](quality-assurance.md) -- [Code Review Guidelines](.pair/knowledge/guidelines/collaboration/README.md) -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) -- [Deployment Workflow](.pair/knowledge/guidelines/technical-standards/deployment-workflow/README.md) +- [Code Review Guidelines](../../collaboration/README.md) +- [Testing Strategy](../../testing/README.md) +- [Deployment Workflow](../deployment-workflow/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/quality-assurance.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/quality-assurance.md index dc7d1bcc..c824baf5 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/quality-assurance.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/quality-assurance.md @@ -1057,6 +1057,6 @@ export class QualityTrainingProgram { - [Development Process](development-process.md) - [Version Control Standards](version-control.md) -- [Testing Strategy](.pair/knowledge/guidelines/testing/README.md) -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- [Code Review Guidelines](.pair/knowledge/guidelines/collaboration/README.md) +- [Testing Strategy](../../testing/README.md) +- [Security Guidelines](../../quality-assurance/security/README.md) +- [Code Review Guidelines](../../collaboration/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/version-control.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/version-control.md index 38dc816d..1d64122e 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/version-control.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/git-workflow/version-control.md @@ -783,6 +783,6 @@ git reset --hard - [Development Process](development-process.md) - [Quality Assurance](quality-assurance.md) -- [Code Review Guidelines](.pair/knowledge/guidelines/collaboration/README.md) -- [Deployment Workflow](.pair/knowledge/guidelines/technical-standards/deployment-workflow/README.md) -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) +- [Code Review Guidelines](../../collaboration/README.md) +- [Deployment Workflow](../deployment-workflow/README.md) +- [Security Guidelines](../../quality-assurance/security/README.md) diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/technology-stack/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/technology-stack/README.md index 64548f50..0f513ccb 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/technology-stack/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/technical-standards/technology-stack/README.md @@ -137,19 +137,19 @@ This section covers technology stack selection and standardization: ## 🔗 Related Practices -- **[Infrastructure](.pair/knowledge/guidelines/infrastructure/README.md)** - Cloud services and deployment platforms for these technologies -- **[Development Tools](.pair/knowledge/guidelines/technical-standards/development-tools/README.md)** - Tools that support these technology choices -- **[Integration Standards](.pair/knowledge/guidelines/technical-standards/integration-standards/README.md)** - How these technologies integrate together -- **[Code Design Framework Patterns](.pair/knowledge/guidelines/code-design/framework-patterns/README.md)** - Implementation patterns for these technologies +- **[Infrastructure](../../infrastructure/README.md)** - Cloud services and deployment platforms for these technologies +- **[Development Tools](../development-tools/README.md)** - Tools that support these technology choices +- **[Integration Standards](../integration-standards/README.md)** - How these technologies integrate together +- **[Code Design Framework Patterns](../../code-design/framework-patterns/README.md)** - Implementation patterns for these technologies ## ☁️ Cloud Integration For cloud deployment and infrastructure automation: -- **[Cloud Providers](.pair/knowledge/guidelines/infrastructure/cloud-providers/README.md)** - Provider selection for tech stack deployment -- **[Container Orchestration](.pair/knowledge/guidelines/infrastructure/container-orchestration/README.md)** - Containerizing and deploying tech stack components -- **[Cloud Services](.pair/knowledge/guidelines/infrastructure/cloud-services/README.md)** - Managed database services aligned with backend stack -- **[CI/CD Strategy](.pair/knowledge/guidelines/infrastructure/cicd-strategy/README.md)** - CI/CD pipelines for tech stack deployment +- **[Cloud Providers](../../infrastructure/cloud-providers/README.md)** - Provider selection for tech stack deployment +- **[Container Orchestration](../../infrastructure/container-orchestration/README.md)** - Containerizing and deploying tech stack components +- **[Cloud Services](../../infrastructure/cloud-services/README.md)** - Managed database services aligned with backend stack +- **[CI/CD Strategy](../../infrastructure/cicd-strategy/README.md)** - CI/CD pipelines for tech stack deployment ## 🎯 Quick Start diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/README.md index 9793081e..1ba8713e 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/README.md @@ -310,10 +310,10 @@ Testing Pipeline: ## 🔗 Related Guidelines -- **[Quality Assurance](.pair/knowledge/guidelines/quality-assurance/README.md)** - Comprehensive quality standards and processes -- **[Code Design](.pair/knowledge/guidelines/code-design/README.md)** - Design patterns supporting testability -- **[Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md)** - Technology standards and testing integration -- **[Infrastructure](.pair/knowledge/guidelines/infrastructure/README.md)** - Testing infrastructure and CI/CD integration +- **[Quality Assurance](../quality-assurance/README.md)** - Comprehensive quality standards and processes +- **[Code Design](../code-design/README.md)** - Design patterns supporting testability +- **[Technical Standards](../technical-standards/README.md)** - Technology standards and testing integration +- **[Infrastructure](../infrastructure/README.md)** - Testing infrastructure and CI/CD integration --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/test-automation/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/test-automation/README.md index 0ae1e0b4..e0e015b5 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/test-automation/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/testing/test-automation/README.md @@ -84,9 +84,9 @@ Consider test maintainability during test design including clear test structure, ## 🔗 Related Practices -- **[Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md)** - Strategic foundation for automation implementation -- **[Unit Testing](.pair/knowledge/guidelines/testing/unit-testing/README.md)** - Unit testing automation practices -- **[Deployment Workflow](.pair/knowledge/guidelines/technical-standards/deployment-workflow/README.md)** - CI/CD integration patterns +- **[Testing Strategy](../test-strategy/README.md)** - Strategic foundation for automation implementation +- **[Unit Testing](../unit-testing/README.md)** - Unit testing automation practices +- **[Deployment Workflow](../../technical-standards/deployment-workflow/README.md)** - CI/CD integration patterns ## 🎯 Quick Start diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/README.md index 3964ce58..eaa1a300 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/README.md @@ -21,9 +21,9 @@ User experience design encompasses the systematic approach to creating intuitive ### Out of Scope -- Technical implementation details (see [Code Design](.pair/knowledge/guidelines/code-design/README.md)) -- Infrastructure and deployment (see [Infrastructure](.pair/knowledge/guidelines/infrastructure/README.md)) -- Security implementation (see [Quality Assurance/Security](.pair/knowledge/guidelines/quality-assurance/security/README.md)) +- Technical implementation details (see [Code Design](../code-design/README.md)) +- Infrastructure and deployment (see [Infrastructure](../infrastructure/README.md)) +- Security implementation (see [Quality Assurance/Security](../quality-assurance/security/README.md)) - Business strategy and market positioning - Legal compliance and regulatory requirements @@ -236,10 +236,10 @@ Component Library Selection: ## 🔗 Related Guidelines -- **[Quality Assurance/Accessibility](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md)** - Accessibility standards implementation -- **[Code Design](.pair/knowledge/guidelines/code-design/README.md)** - Design system technical implementation -- **[Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md)** - Technology standards supporting UX -- **[Collaboration](.pair/knowledge/guidelines/collaboration/README.md)** - Team workflows and process integration +- **[Quality Assurance/Accessibility](../quality-assurance/accessibility/README.md)** - Accessibility standards implementation +- **[Code Design](../code-design/README.md)** - Design system technical implementation +- **[Technical Standards](../technical-standards/README.md)** - Technology standards supporting UX +- **[Collaboration](../collaboration/README.md)** - Team workflows and process integration ## Best Practices diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/content-strategy/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/content-strategy/README.md index 7a4d646e..8c7743a6 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/content-strategy/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/content-strategy/README.md @@ -221,27 +221,27 @@ Content Tool Selection: - **Design Principles**: Content strategy aligns with core design principles for consistent user communication - - [User-Centered Design](.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md) for content that serves user needs - - [Consistency Standards](.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md) for unified voice and messaging - - [Accessibility Integration](.pair/knowledge/guidelines/user-experience/design-principles/accessibility-integration.md) for inclusive content practices + - [User-Centered Design](../design-principles/user-centered-design.md) for content that serves user needs + - [Consistency Standards](../design-principles/consistency-standards.md) for unified voice and messaging + - [Accessibility Integration](../design-principles/accessibility-integration.md) for inclusive content practices - **Design Systems**: Content strategy provides guidelines for system-wide content patterns and messaging - - [Component Libraries](.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md) for content component standardization - - [System Architecture](.pair/knowledge/guidelines/user-experience/design-systems/system-architecture.md) for content governance integration + - [Component Libraries](../design-systems/component-libraries.md) for content component standardization + - [System Architecture](../design-systems/system-architecture.md) for content governance integration - **User Research**: Research insights inform content strategy decisions and messaging effectiveness - - [Research Methods](.pair/knowledge/guidelines/user-experience/user-research/research-methods.md) for content testing and validation approaches + - [Research Methods](../user-research/research-methods.md) for content testing and validation approaches - **Interface Design**: Content strategy guides interface copy, labeling, and communication design - - Interface design documentation in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](.pair/knowledge/guidelines/user-experience/interface-design/README.md) for content-design integration + - Interface design documentation in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](../interface-design/README.md) for content-design integration ### Related Resources -- **[UX Performance](.pair/knowledge/guidelines/user-experience/ux-performance.md)**: Content performance measurement and optimization strategies -- **[Brand Alignment](.pair/knowledge/guidelines/user-experience/brand-alignment.md)**: Ensuring content reflects and reinforces brand identity -- **[Figma Workflows](.pair/knowledge/guidelines/user-experience/figma-workflows.md)**: Content collaboration within design tools -- **[Asset Collection](.pair/knowledge/guidelines/user-experience/asset-collection.md)**: Content asset management and organization systems +- **[UX Performance](../ux-performance.md)**: Content performance measurement and optimization strategies +- **[Brand Alignment](../brand-alignment.md)**: Ensuring content reflects and reinforces brand identity +- **[Figma Workflows](../figma-workflows.md)**: Content collaboration within design tools +- **[Asset Collection](../asset-collection.md)**: Content asset management and organization systems This framework ensures that content strategy creates meaningful, accessible, and effective communication that serves user needs while supporting business objectives and design consistency. diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/README.md index cd7ef565..439c7ce5 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/README.md @@ -244,15 +244,15 @@ User Research → Problem Definition → Solution Design → Validation → Iter ## Integration with Other UX Components -- **Design Systems**: Principles inform system architecture and component behavior standards, detailed in [.pair/knowledge/guidelines/user-experience/design-systems/README.md](.pair/knowledge/guidelines/user-experience/design-systems/README.md) -- **User Research**: Research validates principle effectiveness and informs principle evolution, see [.pair/knowledge/guidelines/user-experience/user-research/README.md](.pair/knowledge/guidelines/user-experience/user-research/README.md) -- **Interface Design**: Principles guide visual and interaction design decision-making, documented in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](.pair/knowledge/guidelines/user-experience/interface-design/README.md) -- **Content Strategy**: Principles shape content approach and communication strategies, outlined in [.pair/knowledge/guidelines/user-experience/content-strategy/README.md](.pair/knowledge/guidelines/user-experience/content-strategy/README.md) +- **Design Systems**: Principles inform system architecture and component behavior standards, detailed in [.pair/knowledge/guidelines/user-experience/design-systems/README.md](../design-systems/README.md) +- **User Research**: Research validates principle effectiveness and informs principle evolution, see [.pair/knowledge/guidelines/user-experience/user-research/README.md](../user-research/README.md) +- **Interface Design**: Principles guide visual and interaction design decision-making, documented in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](../interface-design/README.md) +- **Content Strategy**: Principles shape content approach and communication strategies, outlined in [.pair/knowledge/guidelines/user-experience/content-strategy/README.md](../content-strategy/README.md) ### Related Resources -- **[UX Performance Guidelines](.pair/knowledge/guidelines/user-experience/ux-performance.md)**: Performance impact of design principle implementation -- **[Brand Alignment](.pair/knowledge/guidelines/user-experience/brand-alignment.md)**: Aligning design principles with brand strategy -- **[Figma Workflows](.pair/knowledge/guidelines/user-experience/figma-workflows.md)**: Tool-specific implementation of design principles +- **[UX Performance Guidelines](../ux-performance.md)**: Performance impact of design principle implementation +- **[Brand Alignment](../brand-alignment.md)**: Aligning design principles with brand strategy +- **[Figma Workflows](../figma-workflows.md)**: Tool-specific implementation of design principles This framework ensures that design principles serve as actionable guidance for creating exceptional user experiences while supporting business objectives and technical constraints. diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md index 6db3076d..007e9e10 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md @@ -308,10 +308,10 @@ Create systematic consistency standards that enable users to develop mental mode ## 🔗 Related Practices -- **[Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/README.md)** - Component libraries and systematic design implementation +- **[Design Systems](../design-systems/README.md)** - Component libraries and systematic design implementation - **[User-Centered Design](user-centered-design.md)** - User research validation for consistency effectiveness -- **[Accessibility Guidelines](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md)** - Inclusive consistency across all user abilities -- **[Brand Guidelines](.pair/knowledge/guidelines/user-experience/brand-alignment.md)** - Brand consistency integration with user experience standards +- **[Accessibility Guidelines](../../quality-assurance/accessibility/README.md)** - Inclusive consistency across all user abilities +- **[Brand Guidelines](../brand-alignment.md)** - Brand consistency integration with user experience standards --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md index 30d84adb..bc09b125 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md @@ -316,10 +316,10 @@ Establish user-centered design as the foundation for all product decisions, ensu ## 🔗 Related Practices -- **[Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/README.md)** - Component and pattern design with user-centered principles -- **[Accessibility Guidelines](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md)** - Inclusive design implementation and compliance -- **[User Research Methods](.pair/knowledge/guidelines/user-experience/user-research/README.md)** - Specific research methodologies and execution -- **[Content Strategy](.pair/knowledge/guidelines/user-experience/content-strategy/README.md)** - User-centered content design and information architecture +- **[Design Systems](../design-systems/README.md)** - Component and pattern design with user-centered principles +- **[Accessibility Guidelines](../../quality-assurance/accessibility/README.md)** - Inclusive design implementation and compliance +- **[User Research Methods](../user-research/README.md)** - Specific research methodologies and execution +- **[Content Strategy](../content-strategy/README.md)** - User-centered content design and information architecture --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/README.md index c70971d9..8f391c05 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/README.md @@ -249,15 +249,15 @@ Community → Core Team → Spike → Validation → Release → Knowledge Base ## Integration with Other UX Components -- **Design Principles**: System architecture embodies and enforces design principles, detailed in [.pair/knowledge/guidelines/user-experience/design-principles/README.md](.pair/knowledge/guidelines/user-experience/design-principles/README.md) -- **User Research**: Research insights inform component design and system evolution, see [.pair/knowledge/guidelines/user-experience/user-research/README.md](.pair/knowledge/guidelines/user-experience/user-research/README.md) -- **Interface Design**: System provides the building blocks for interface design execution, documented in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](.pair/knowledge/guidelines/user-experience/interface-design/README.md) -- **Content Strategy**: System includes content patterns and messaging guidelines, outlined in [.pair/knowledge/guidelines/user-experience/content-strategy/README.md](.pair/knowledge/guidelines/user-experience/content-strategy/README.md) +- **Design Principles**: System architecture embodies and enforces design principles, detailed in [.pair/knowledge/guidelines/user-experience/design-principles/README.md](../design-principles/README.md) +- **User Research**: Research insights inform component design and system evolution, see [.pair/knowledge/guidelines/user-experience/user-research/README.md](../user-research/README.md) +- **Interface Design**: System provides the building blocks for interface design execution, documented in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](../interface-design/README.md) +- **Content Strategy**: System includes content patterns and messaging guidelines, outlined in [.pair/knowledge/guidelines/user-experience/content-strategy/README.md](../content-strategy/README.md) ### Related Resources -- **[Figma Workflows](.pair/knowledge/guidelines/user-experience/figma-workflows.md)**: Design system implementation in Figma -- **[Brand Alignment](.pair/knowledge/guidelines/user-experience/brand-alignment.md)**: Ensuring design system reflects brand identity -- **[Asset Collection](.pair/knowledge/guidelines/user-experience/asset-collection.md)**: Managing design system assets and resources +- **[Figma Workflows](../figma-workflows.md)**: Design system implementation in Figma +- **[Brand Alignment](../brand-alignment.md)**: Ensuring design system reflects brand identity +- **[Asset Collection](../asset-collection.md)**: Managing design system assets and resources This framework ensures that design systems serve as the scalable foundation for consistent, accessible, and high-quality user experiences across all digital touchpoints. diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md index faa5fa85..9f2b36f1 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md @@ -273,8 +273,8 @@ Establish comprehensive component library practices that enable scalable design - **[Design Systems](README.md)** - Overall design system strategy and implementation - **[Design Tokens](design-tokens.md)** - Token integration and component styling consistency -- **[User-Centered Design](.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md)** - User research integration for component development -- **[Accessibility Guidelines](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md)** - Accessibility implementation and compliance +- **[User-Centered Design](../design-principles/user-centered-design.md)** - User research integration for component development +- **[Accessibility Guidelines](../../quality-assurance/accessibility/README.md)** - Accessibility implementation and compliance --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/design-tokens.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/design-tokens.md index 3463de97..9c3075cf 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/design-tokens.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/design-systems/design-tokens.md @@ -265,8 +265,8 @@ Establish design tokens as the foundational layer of design systems, ensuring co - **[Design Systems](README.md)** - Overall design system strategy and component integration - **[Component Libraries](component-libraries.md)** - Component implementation using design tokens -- **[Consistency Standards](.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md)** - Visual consistency through systematic token usage -- **[Accessibility Guidelines](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md)** - Accessible design through compliant token values +- **[Consistency Standards](../design-principles/consistency-standards.md)** - Visual consistency through systematic token usage +- **[Accessibility Guidelines](../../quality-assurance/accessibility/README.md)** - Accessible design through compliant token values --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/interface-design/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/interface-design/README.md index d5344af9..bd16e292 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/interface-design/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/interface-design/README.md @@ -185,11 +185,11 @@ Single Column → Multi-Column → Complex Layouts → Enhanced Functionality | Design Complexity | Focus Areas | Related Resources | Implementation Timeline | | ------------------------ | ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ----------------------- | -| **Simple Interface** | Visual hierarchy + [Design Principles](.pair/knowledge/guidelines/user-experience/design-principles/typography.md) | [Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md) | 2-4 weeks | -| **Complex Dashboard** | Component architecture + [Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/system-architecture.md) | [User Research](.pair/knowledge/guidelines/user-experience/user-research/research-methods.md) for validation | 6-10 weeks | -| **Multi-Platform** | Responsive design + [Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/design-tokens.md) | [Design Principles](.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md) | 8-12 weeks | -| **Accessibility Focus** | Inclusive design + [Design Principles](.pair/knowledge/guidelines/user-experience/design-principles/accessibility-integration.md) | [Design Principles](.pair/knowledge/guidelines/user-experience/design-principles/color-contrast.md) | 4-6 weeks | -| **Performance Critical** | Optimization + [UX Performance](.pair/knowledge/guidelines/user-experience/ux-performance.md) | [Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/README.md) efficiency patterns | 3-5 weeks | +| **Simple Interface** | Visual hierarchy + [Design Principles](../design-principles/typography.md) | [Design Systems](../design-systems/component-libraries.md) | 2-4 weeks | +| **Complex Dashboard** | Component architecture + [Design Systems](../design-systems/system-architecture.md) | [User Research](../user-research/research-methods.md) for validation | 6-10 weeks | +| **Multi-Platform** | Responsive design + [Design Systems](../design-systems/design-tokens.md) | [Design Principles](../design-principles/consistency-standards.md) | 8-12 weeks | +| **Accessibility Focus** | Inclusive design + [Design Principles](../design-principles/accessibility-integration.md) | [Design Principles](../design-principles/color-contrast.md) | 4-6 weeks | +| **Performance Critical** | Optimization + [UX Performance](../ux-performance.md) | [Design Systems](../design-systems/README.md) efficiency patterns | 3-5 weeks | ## Interface Design Tool Selection Matrix @@ -203,39 +203,39 @@ Single Column → Multi-Column → Complex Layouts → Enhanced Functionality **Tool Integration Resources**: -- **Figma Workflows**: See [.pair/knowledge/guidelines/user-experience/figma-workflows.md](.pair/knowledge/guidelines/user-experience/figma-workflows.md) for design tool optimization -- **Design System Integration**: [Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md) for component handoff -- **Asset Management**: [.pair/knowledge/guidelines/user-experience/asset-collection.md](.pair/knowledge/guidelines/user-experience/asset-collection.md) for interface asset organization +- **Figma Workflows**: See [.pair/knowledge/guidelines/user-experience/figma-workflows.md](../figma-workflows.md) for design tool optimization +- **Design System Integration**: [Design Systems](../design-systems/component-libraries.md) for component handoff +- **Asset Management**: [.pair/knowledge/guidelines/user-experience/asset-collection.md](../asset-collection.md) for interface asset organization ## Integration with Other UX Components - **Design Principles**: Interface design embodies and applies core design principles in visual and interactive form - - [User-Centered Design](.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md) for user needs prioritization - - [Consistency Standards](.pair/knowledge/guidelines/user-experience/design-principles/consistency-standards.md) for cross-platform coherence - - [Accessibility Integration](.pair/knowledge/guidelines/user-experience/design-principles/accessibility-integration.md) for inclusive interfaces - - [Typography](.pair/knowledge/guidelines/user-experience/design-principles/typography.md) and [Color Contrast](.pair/knowledge/guidelines/user-experience/design-principles/color-contrast.md) for visual hierarchy + - [User-Centered Design](../design-principles/user-centered-design.md) for user needs prioritization + - [Consistency Standards](../design-principles/consistency-standards.md) for cross-platform coherence + - [Accessibility Integration](../design-principles/accessibility-integration.md) for inclusive interfaces + - [Typography](../design-principles/typography.md) and [Color Contrast](../design-principles/color-contrast.md) for visual hierarchy - **Design Systems**: Interface design creates and utilizes design system components and patterns - - [System Architecture](.pair/knowledge/guidelines/user-experience/design-systems/system-architecture.md) for scalable interface foundations - - [Component Libraries](.pair/knowledge/guidelines/user-experience/design-systems/component-libraries.md) for reusable interface elements - - [Design Tokens](.pair/knowledge/guidelines/user-experience/design-systems/design-tokens.md) for consistent visual properties + - [System Architecture](../design-systems/system-architecture.md) for scalable interface foundations + - [Component Libraries](../design-systems/component-libraries.md) for reusable interface elements + - [Design Tokens](../design-systems/design-tokens.md) for consistent visual properties - **User Research**: Research insights directly inform interface design decisions and validation processes - - [Research Methods](.pair/knowledge/guidelines/user-experience/user-research/research-methods.md) for interface usability testing and optimization + - [Research Methods](../user-research/research-methods.md) for interface usability testing and optimization - **Content Strategy**: Interface design incorporates content strategy principles for effective communication - - [Content Guidelines](.pair/knowledge/guidelines/user-experience/content-strategy/content-guidelines.md) for interface copy and messaging - - [Information Architecture](.pair/knowledge/guidelines/user-experience/content-strategy/information-architecture.md) for interface structure - - [Communication Design](.pair/knowledge/guidelines/user-experience/content-strategy/communication-design.md) for user interface communication + - [Content Guidelines](../content-strategy/content-guidelines.md) for interface copy and messaging + - [Information Architecture](../content-strategy/information-architecture.md) for interface structure + - [Communication Design](../content-strategy/communication-design.md) for user interface communication ### Related Resources -- **[UX Performance](.pair/knowledge/guidelines/user-experience/ux-performance.md)**: Interface performance optimization and measurement -- **[Brand Alignment](.pair/knowledge/guidelines/user-experience/brand-alignment.md)**: Ensuring interface design reflects brand identity -- **[Figma Workflows](.pair/knowledge/guidelines/user-experience/figma-workflows.md)**: Interface design implementation in Figma -- **[Asset Collection](.pair/knowledge/guidelines/user-experience/asset-collection.md)**: Managing interface design assets and resources +- **[UX Performance](../ux-performance.md)**: Interface performance optimization and measurement +- **[Brand Alignment](../brand-alignment.md)**: Ensuring interface design reflects brand identity +- **[Figma Workflows](../figma-workflows.md)**: Interface design implementation in Figma +- **[Asset Collection](../asset-collection.md)**: Managing interface design assets and resources This framework ensures that interface design creates compelling, accessible, and effective user interfaces that serve user needs while supporting business objectives and technical requirements. diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/README.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/README.md index cbb0aaa6..92b7def3 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/README.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/README.md @@ -220,10 +220,10 @@ Strategic Goals → User Insights → Methodology → Evidence | Research Objective | Primary Method | Documentation | Timeline | Integration Points | | ------------------------- | ------------------------------------------------------------- | ---------------------------------------------------- | --------- | ------------------------------------------------------------------ | -| **Problem Discovery** | Ethnographic + [Research Methods](research-methods.md) | User journey analysis + Contextual inquiry protocols | 2-4 weeks | [Design Principles](.pair/knowledge/guidelines/user-experience/design-principles/README.md) validation | -| **Concept Validation** | Prototype testing + [Research Methods](research-methods.md) | Usability testing protocols + A/B testing setup | 1-2 weeks | [Interface Design](.pair/knowledge/guidelines/user-experience/interface-design/README.md) optimization | -| **Design Optimization** | Usability testing + [Research Methods](research-methods.md) | Task analysis + Performance metrics | 1-3 weeks | [Design Systems](.pair/knowledge/guidelines/user-experience/design-systems/README.md) component validation | -| **Strategy Development** | Market research + [Research Methods](research-methods.md) | Competitive analysis + Persona development | 4-8 weeks | [Content Strategy](.pair/knowledge/guidelines/user-experience/content-strategy/README.md) alignment | +| **Problem Discovery** | Ethnographic + [Research Methods](research-methods.md) | User journey analysis + Contextual inquiry protocols | 2-4 weeks | [Design Principles](../design-principles/README.md) validation | +| **Concept Validation** | Prototype testing + [Research Methods](research-methods.md) | Usability testing protocols + A/B testing setup | 1-2 weeks | [Interface Design](../interface-design/README.md) optimization | +| **Design Optimization** | Usability testing + [Research Methods](research-methods.md) | Task analysis + Performance metrics | 1-3 weeks | [Design Systems](../design-systems/README.md) component validation | +| **Strategy Development** | Market research + [Research Methods](research-methods.md) | Competitive analysis + Persona development | 4-8 weeks | [Content Strategy](../content-strategy/README.md) alignment | | **Continuous Monitoring** | Analytics + [Research Methods](research-methods.md) | Dashboard setup + Feedback collection | Ongoing | All UX components integration | ## Research Method Selection Matrix @@ -244,15 +244,15 @@ Strategic Goals → User Insights → Methodology → Evidence ## Integration with Other UX Components -- **Design Principles**: Research validates and informs principle effectiveness and evolution, detailed in [.pair/knowledge/guidelines/user-experience/design-principles/README.md](.pair/knowledge/guidelines/user-experience/design-principles/README.md) -- **Design Systems**: User research guides component design and system architecture decisions, see [.pair/knowledge/guidelines/user-experience/design-systems/README.md](.pair/knowledge/guidelines/user-experience/design-systems/README.md) -- **Interface Design**: Research insights directly inform interface design choices and optimization, documented in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](.pair/knowledge/guidelines/user-experience/interface-design/README.md) -- **Content Strategy**: User research provides foundation for content approach and messaging strategy, outlined in [.pair/knowledge/guidelines/user-experience/content-strategy/README.md](.pair/knowledge/guidelines/user-experience/content-strategy/README.md) +- **Design Principles**: Research validates and informs principle effectiveness and evolution, detailed in [.pair/knowledge/guidelines/user-experience/design-principles/README.md](../design-principles/README.md) +- **Design Systems**: User research guides component design and system architecture decisions, see [.pair/knowledge/guidelines/user-experience/design-systems/README.md](../design-systems/README.md) +- **Interface Design**: Research insights directly inform interface design choices and optimization, documented in [.pair/knowledge/guidelines/user-experience/interface-design/README.md](../interface-design/README.md) +- **Content Strategy**: User research provides foundation for content approach and messaging strategy, outlined in [.pair/knowledge/guidelines/user-experience/content-strategy/README.md](../content-strategy/README.md) ### Related Resources -- **[UX Performance](.pair/knowledge/guidelines/user-experience/ux-performance.md)**: Performance impact measurement and optimization -- **[Brand Alignment](.pair/knowledge/guidelines/user-experience/brand-alignment.md)**: Research methods for brand perception and alignment -- **[Asset Collection](.pair/knowledge/guidelines/user-experience/asset-collection.md)**: Research asset management and repository organization +- **[UX Performance](../ux-performance.md)**: Performance impact measurement and optimization +- **[Brand Alignment](../brand-alignment.md)**: Research methods for brand perception and alignment +- **[Asset Collection](../asset-collection.md)**: Research asset management and repository organization This framework ensures that user research provides actionable insights that drive user-centered design decisions and create measurable business value through deep user understanding. diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/research-methods.md b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/research-methods.md index e5fca158..30d4e9d4 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/research-methods.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/guidelines/user-experience/user-research/research-methods.md @@ -284,10 +284,10 @@ Establish a robust toolkit of research methods that enable teams to understand u ## 🔗 Related Practices -- **[User-Centered Design](.pair/knowledge/guidelines/user-experience/design-principles/user-centered-design.md)** - Design process integration with research findings +- **[User-Centered Design](../design-principles/user-centered-design.md)** - Design process integration with research findings - **[Testing and Validation](testing-validation.md)** - Usability testing and design validation methods - **[User Feedback Systems](user-feedback.md)** - Continuous feedback collection and analysis -- **[Analytics and Metrics](.pair/knowledge/guidelines/observability/metrics/README.md)** - Quantitative analysis and measurement integration +- **[Analytics and Metrics](../../observability/metrics/README.md)** - Quantitative analysis and measurement integration --- diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/01-how-to-create-PRD.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/01-how-to-create-PRD.md index a87ca04d..6ede1980 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/01-how-to-create-PRD.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/01-how-to-create-PRD.md @@ -29,11 +29,11 @@ PRD CREATION STATE: ### Template-First PRD Creation -- **Study reference materials FIRST** - analyze [PRD template](.pair/knowledge/assets/PRD_template.md) and [PRD example](.pair/knowledge/assets/PRD_example.md) +- **Study reference materials FIRST** - analyze [PRD template](../assets/PRD_template.md) and [PRD example](../assets/PRD_example.md) - **Follow template structure exactly** - use all sections from template - **Match example quality standard** - specificity, metrics, professional tone - **Create comprehensive information checklist** based on template sections -- **Target file**: [`.pair/adoption/product/PRD.md`](.pair/adoption/product/PRD.md) +- **Target file**: [`.pair/adoption/product/PRD.md`](../../adoption/product/PRD.md) **CRITICAL**: Before starting information gathering: @@ -48,8 +48,8 @@ PRD CREATION STATE: **Before starting**: Review reference materials to understand structure and quality standards. -1. **Analyze template structure** from [PRD template](.pair/knowledge/assets/PRD_template.md) -2. **Study quality standards** from [PRD example](.pair/knowledge/assets/PRD_example.md) +1. **Analyze template structure** from [PRD template](../assets/PRD_template.md) +2. **Study quality standards** from [PRD example](../assets/PRD_example.md) 3. **Create comprehensive checklist** mapping all template sections 4. **Update session state** with template analysis complete @@ -87,10 +87,10 @@ PRD CREATION STATE: **Objective**: Create comprehensive PRD using gathered information. -1. **Create PRD file** at [`.pair/adoption/product/PRD.md`](.pair/adoption/product/PRD.md) -2. **Use template structure** from [PRD template](.pair/knowledge/assets/PRD_template.md) -3. **Match quality standards** from [PRD example](.pair/knowledge/assets/PRD_example.md) -4. **Apply writing guidelines** per [documentation standards](.pair/knowledge/guidelines/README.md) +1. **Create PRD file** at [`.pair/adoption/product/PRD.md`](../../adoption/product/PRD.md) +2. **Use template structure** from [PRD template](../assets/PRD_template.md) +3. **Match quality standards** from [PRD example](../assets/PRD_example.md) +4. **Apply writing guidelines** per [documentation standards](../guidelines/README.md) ### Phase 3: Review & Approval @@ -121,11 +121,11 @@ PRD CREATION STATE: ### PRD Creation Guidelines -**Follow template structure exactly** - use [PRD template](.pair/knowledge/assets/PRD_template.md): +**Follow template structure exactly** - use [PRD template](../assets/PRD_template.md): -- Copy template into [`.pair/adoption/product/PRD.md`](.pair/adoption/product/PRD.md) +- Copy template into [`.pair/adoption/product/PRD.md`](../../adoption/product/PRD.md) - Replace all placeholders with gathered information -- Match quality standard from [PRD example](.pair/knowledge/assets/PRD_example.md) +- Match quality standard from [PRD example](../assets/PRD_example.md) - Use clear, actionable language with specific details and measurable criteria **Writing Quality Requirements:** @@ -179,7 +179,7 @@ PRD CREATION STATE: - [ ] No assumptions made without validation - [ ] All stakeholder needs considered - [ ] Document provides sufficient detail for development team -- [ ] Final document saved in [`.pair/adoption/product/PRD.md`](.pair/adoption/product/PRD.md) +- [ ] Final document saved in [`.pair/adoption/product/PRD.md`](../../adoption/product/PRD.md) --- @@ -187,18 +187,18 @@ PRD CREATION STATE: **Primary Templates & Examples:** -- [PRD Template](.pair/knowledge/assets/PRD_template.md) - Complete structure and sections -- [PRD Example](.pair/knowledge/assets/PRD_example.md) - Quality standards and writing style +- [PRD Template](../assets/PRD_template.md) - Complete structure and sections +- [PRD Example](../assets/PRD_example.md) - Quality standards and writing style **Implementation Guidelines:** -- [Documentation Standards](.pair/knowledge/guidelines/README.md) - Writing and formatting guidelines -- [Collaboration Guidelines](.pair/knowledge/guidelines/collaboration/README.md) - Question asking and review processes -- [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) - User story format standards +- [Documentation Standards](../guidelines/README.md) - Writing and formatting guidelines +- [Collaboration Guidelines](../guidelines/collaboration/README.md) - Question asking and review processes +- [User Story Template](../guidelines/collaboration/templates/user-story-template.md) - User story format standards **Target Output:** -- [Final PRD Location](.pair/adoption/product/PRD.md) - Where completed PRD is saved and maintained +- [Final PRD Location](../../adoption/product/PRD.md) - Where completed PRD is saved and maintained ## Next Steps diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/02-how-to-complete-bootstrap-checklist.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/02-how-to-complete-bootstrap-checklist.md index ab10880b..a8f450cd 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/02-how-to-complete-bootstrap-checklist.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/02-how-to-complete-bootstrap-checklist.md @@ -48,7 +48,7 @@ BOOTSTRAP COMPLETION STATE: **Before starting**: Analyze existing project documentation to understand context. -1. **Read PRD** from [`.pair/adoption/product/PRD.md`](.pair/adoption/product/PRD.md) +1. **Read PRD** from [`.pair/adoption/product/PRD.md`](../../adoption/product/PRD.md) 2. **Extract key constraints**: - Target users and scale expectations - Budget and timeline constraints @@ -81,7 +81,7 @@ BOOTSTRAP COMPLETION STATE: 3. **Handle categorization feedback** and proceed when confirmed -**Project Categories Reference**: [Bootstrap Checklist](.pair/knowledge/assets/bootstrap-checklist.md) +**Project Categories Reference**: [Bootstrap Checklist](../assets/bootstrap-checklist.md) ### Phase 2: Checklist Completion @@ -110,8 +110,8 @@ BOOTSTRAP COMPLETION STATE: **Ask 3-4 focused questions at a time** and wait for responses before proceeding. -**Architecture Guidelines Reference**: [Architecture Guidelines](.pair/knowledge/guidelines/architecture/README.md) -**Technical Standards Reference**: [Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md) +**Architecture Guidelines Reference**: [Architecture Guidelines](../guidelines/architecture/README.md) +**Technical Standards Reference**: [Technical Standards](../guidelines/technical-standards/README.md) ### Phase 3: Standards Document Generation @@ -134,16 +134,16 @@ BOOTSTRAP COMPLETION STATE: - Iterate based on feedback - Get final approval before saving -3. **Standards Format Requirements**: [Adopted Standards README](.pair/adoption/tech/README.md) +3. **Standards Format Requirements**: [Adopted Standards README](../../adoption/tech/README.md) -**Infrastructure Guidelines Reference**: [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) -**UX Guidelines Reference**: [UX Guidelines](.pair/knowledge/guidelines/user-experience/README.md) +**Infrastructure Guidelines Reference**: [Infrastructure Guidelines](../guidelines/infrastructure/README.md) +**UX Guidelines Reference**: [UX Guidelines](../guidelines/user-experience/README.md) ### Phase 4: Finalization & Storage **Objective**: Save approved documents and establish update process. -1. **Save all documents** to [`.pair/adoption/tech/`](.pair/adoption/tech) folder +1. **Save all documents** to [`.pair/adoption/tech/`](../../adoption/tech) folder 2. **Verify consistency** across all standards documents 3. **Establish update process** for future iterations and ADR changes 4. **Update session state** to approved status @@ -162,7 +162,7 @@ BOOTSTRAP COMPLETION STATE: **Document Quality Requirements**: -- Follow [adopted standards format](.pair/adoption/tech/README.md) exactly +- Follow [adopted standards format](../../adoption/tech/README.md) exactly - Write concisely and prescriptively in English - Include specific versions and configuration details - Reference knowledge-base documents for detailed rationale @@ -195,7 +195,7 @@ BOOTSTRAP COMPLETION STATE: - [ ] Bootstrap checklist fully completed with all sections addressed - [ ] Project categorization confirmed and documented - [ ] All five adopted standards documents generated and approved -- [ ] Documents stored in correct [`.pair/adoption/tech/`](.pair/adoption/tech) locations +- [ ] Documents stored in correct [`.pair/adoption/tech/`](../../adoption/tech) locations **Quality:** @@ -211,24 +211,24 @@ BOOTSTRAP COMPLETION STATE: **Primary Implementation Assets:** -- [Bootstrap Checklist](.pair/knowledge/assets/bootstrap-checklist.md) - Complete project setup framework -- [Adopted Standards README](.pair/adoption/tech/README.md) - Format requirements for all documents +- [Bootstrap Checklist](../assets/bootstrap-checklist.md) - Complete project setup framework +- [Adopted Standards README](../../adoption/tech/README.md) - Format requirements for all documents **Guidelines for Implementation:** -- [Architecture Guidelines](.pair/knowledge/guidelines/architecture/README.md) - Architectural patterns and decisions -- [Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md) - Technology selection criteria -- [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) - Deployment and operational guidance -- [UX Guidelines](.pair/knowledge/guidelines/user-experience/README.md) - Design system and user experience standards -- [Collaboration Guidelines](.pair/knowledge/guidelines/collaboration/README.md) - Development processes and team workflows +- [Architecture Guidelines](../guidelines/architecture/README.md) - Architectural patterns and decisions +- [Technical Standards](../guidelines/technical-standards/README.md) - Technology selection criteria +- [Infrastructure Guidelines](../guidelines/infrastructure/README.md) - Deployment and operational guidance +- [UX Guidelines](../guidelines/user-experience/README.md) - Design system and user experience standards +- [Collaboration Guidelines](../guidelines/collaboration/README.md) - Development processes and team workflows **Target Output Locations:** -- [Architecture Standards](.pair/adoption/tech/architecture.md) - System design decisions -- [Tech Stack Standards](.pair/adoption/tech/tech-stack.md) - Technology choices and versions -- [Infrastructure Standards](.pair/adoption/tech/infrastructure.md) - Deployment and operations -- [UX/UI Standards](.pair/adoption/tech/ux-ui.md) - Design system and patterns -- [Way of Working](.pair/adoption/tech/way-of-working.md) - Development processes +- [Architecture Standards](../../adoption/tech/architecture.md) - System design decisions +- [Tech Stack Standards](../../adoption/tech/tech-stack.md) - Technology choices and versions +- [Infrastructure Standards](../../adoption/tech/infrastructure.md) - Deployment and operations +- [UX/UI Standards](../../adoption/tech/ux-ui.md) - Design system and patterns +- [Way of Working](../../adoption/tech/way-of-working.md) - Development processes ## Next Steps diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md index 80315c28..39affcc5 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/03-how-to-create-and-prioritize-initiatives.md @@ -32,7 +32,7 @@ INITIATIVE CREATION STATE: - **Analyze PRD systematically** - extract business objectives, user value, and constraints - **Prioritize by business impact** - use P0/P1/P2 framework aligned with PRD goals - **Create collaboratively** - validate each initiative through structured feedback loops -- **Document comprehensively** - follow [Initiative Template](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) +- **Document comprehensively** - follow [Initiative Template](../guidelines/collaboration/templates/initiative-template.md) - **Plan dependencies** - establish timeline and resource requirements **CRITICAL**: Before starting initiative creation: @@ -50,15 +50,15 @@ INITIATIVE CREATION STATE: 1. **Check Bootstrap Status**: - - PRD exists and is complete: [`.pair/product/adopted/PRD.md`](.pair/adoption/product/PRD.md) - - Technical standards established: [`.pair/adoption/tech/`](.pair/adoption/tech) - - Project management tool configured: [`.pair/adoption/tech/way-of-working.md`](.pair/adoption/tech/way-of-working.md) + - PRD exists and is complete: [`.pair/product/adopted/PRD.md`](../../adoption/product/PRD.md) + - Technical standards established: [`.pair/adoption/tech/`](../../adoption/tech) + - Project management tool configured: [`.pair/adoption/tech/way-of-working.md`](../../adoption/tech/way-of-working.md) 2. **Configure Project Management Access**: - **Read tool configuration** from way-of-working.md - - **Follow tool-specific guidelines**: [Project Management Framework](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - - **Prepare initiative template**: [Initiative Template](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) + - **Follow tool-specific guidelines**: [Project Management Framework](../guidelines/collaboration/project-management-tool/README.md) + - **Prepare initiative template**: [Initiative Template](../guidelines/collaboration/templates/initiative-template.md) 3. **Handle Missing Configuration**: @@ -100,7 +100,7 @@ INITIATIVE CREATION STATE: _Does this prioritization align with your business strategy? What would you adjust?"_ -**Analysis Guidelines**: [Business Value Assessment](.pair/knowledge/guidelines/quality-assurance/performance/continuous-improvement.md#business-value-assessment) +**Analysis Guidelines**: [Business Value Assessment](../guidelines/quality-assurance/performance/continuous-improvement.md#business-value-assessment) ### Phase 3: Initiative Creation @@ -110,7 +110,7 @@ INITIATIVE CREATION STATE: 1. **Initiative Draft Creation**: - - Present complete initiative using [Initiative Template](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) + - Present complete initiative using [Initiative Template](../guidelines/collaboration/templates/initiative-template.md) - Focus on business rationale, scope definition, and success metrics - Include risk assessment and mitigation strategies - Propose timeline and resource estimates @@ -127,7 +127,7 @@ INITIATIVE CREATION STATE: - Confirm risk assessment and mitigation plans 4. **Tool-Specific Documentation**: - - **Follow tool guidelines**: [Project Management Framework](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) + - **Follow tool guidelines**: [Project Management Framework](../guidelines/collaboration/project-management-tool/README.md) - Create initiative in configured project management tool - Ensure proper labeling, priority assignment, and organization - Maintain cross-references and documentation links @@ -166,7 +166,7 @@ INITIATIVE CREATION STATE: - Establish process for initiative updates and iterations - Verify tool integration for next development phase -**Planning Reference**: [Roadmap Planning Guidelines](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md#quarterly-roadmap) +**Planning Reference**: [Roadmap Planning Guidelines](../guidelines/collaboration/templates/initiative-template.md#quarterly-roadmap) ## Quality Standards @@ -182,7 +182,7 @@ INITIATIVE CREATION STATE: **Documentation Standards**: -- [ ] Follows [Initiative Template](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) structure completely +- [ ] Follows [Initiative Template](../guidelines/collaboration/templates/initiative-template.md) structure completely - [ ] Uses consistent terminology with PRD and technical standards - [ ] Maintains proper tool-specific formatting and metadata - [ ] Includes appropriate cross-references and documentation links @@ -200,7 +200,7 @@ INITIATIVE CREATION STATE: **Do's:** - Start with comprehensive PRD analysis to understand business context -- Follow [Project Management Framework](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) consistently +- Follow [Project Management Framework](../guidelines/collaboration/project-management-tool/README.md) consistently - Focus on one initiative at a time for quality and engagement - Connect each initiative to specific business value and measurable outcomes - Validate assumptions through targeted questions rather than presumptions @@ -231,18 +231,18 @@ INITIATIVE CREATION STATE: **Primary Implementation Assets:** -- [Initiative Template](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) - Complete structure and fields for initiative documentation -- [Project Management Framework](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - Tool-specific guidelines and access procedures +- [Initiative Template](../guidelines/collaboration/templates/initiative-template.md) - Complete structure and fields for initiative documentation +- [Project Management Framework](../guidelines/collaboration/project-management-tool/README.md) - Tool-specific guidelines and access procedures **Guidelines for Implementation:** -- [Business Value Assessment](.pair/knowledge/guidelines/quality-assurance/performance/continuous-improvement.md#business-value-assessment) - Framework for analyzing and prioritizing business impact -- [Roadmap Planning Guidelines](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md#quarterly-roadmap) - Timeline and dependency management best practices +- [Business Value Assessment](../guidelines/quality-assurance/performance/continuous-improvement.md#business-value-assessment) - Framework for analyzing and prioritizing business impact +- [Roadmap Planning Guidelines](../guidelines/collaboration/templates/initiative-template.md#quarterly-roadmap) - Timeline and dependency management best practices **Prerequisite Documentation:** -- [`.pair/product/adopted/PRD.md`](.pair/adoption/product/PRD.md) - Product Requirements Document with business objectives -- [`.pair/adoption/tech/way-of-working.md`](.pair/adoption/tech/way-of-working.md) - Project management tool configuration +- [`.pair/product/adopted/PRD.md`](../../adoption/product/PRD.md) - Product Requirements Document with business objectives +- [`.pair/adoption/tech/way-of-working.md`](../../adoption/tech/way-of-working.md) - Project management tool configuration - [Bootstrap Checklist](02-how-to-complete-bootstrap-checklist.md) - Process for establishing foundational documentation ## Next Steps diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/04-how-to-define-subdomains.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/04-how-to-define-subdomains.md index 44e8aedd..cba2b354 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/04-how-to-define-subdomains.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/04-how-to-define-subdomains.md @@ -32,9 +32,9 @@ SUBDOMAIN DEFINITION STATE: - **Analyze PRD and initiatives systematically** - extract business capabilities and strategic priorities - **Apply DDD classification framework** - core/supporting/generic based on business value and complexity - **Create catalog before details** - validate complete subdomain landscape first, then define individually -- **Follow DDD implementation patterns**: [Domain-Driven Design Guidelines](.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md) -- **Apply strategic subdomain framework**: [Strategic Subdomain Definition](.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md) -- **Document with standards**: [Documentation Guidelines](.pair/knowledge/guidelines/README.md) +- **Follow DDD implementation patterns**: [Domain-Driven Design Guidelines](../guidelines/architecture/design-patterns/domain-driven-design.md) +- **Apply strategic subdomain framework**: [Strategic Subdomain Definition](../guidelines/architecture/design-patterns/strategic-subdomain-definition.md) +- **Document with standards**: [Documentation Guidelines](../guidelines/README.md) **CRITICAL**: Before starting subdomain definition: @@ -51,9 +51,9 @@ SUBDOMAIN DEFINITION STATE: 1. **Check Prerequisites**: - - PRD exists and complete: [`.pair/product/adopted/PRD.md`](.pair/adoption/product/PRD.md) - - Initiatives identified: Following [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - - Bootstrap complete: [`.pair/adoption/tech/`](.pair/adoption/tech) + - PRD exists and complete: [`.pair/product/adopted/PRD.md`](../../adoption/product/PRD.md) + - Initiatives identified: Following [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) + - Bootstrap complete: [`.pair/adoption/tech/`](../../adoption/tech) 2. **Configure Domain Analysis Context**: @@ -104,7 +104,7 @@ SUBDOMAIN DEFINITION STATE: _Does this catalog accurately represent your business domain? What adjustments are needed?"_ 3. **Domain Relationship Mapping**: - - Apply [DDD Context Mapping](.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md) patterns + - Apply [DDD Context Mapping](../guidelines/architecture/design-patterns/domain-driven-design.md) patterns - Identify integration complexity and coordination requirements - Map data flow and dependency patterns between subdomains @@ -147,11 +147,11 @@ SUBDOMAIN DEFINITION STATE: 1. **File Generation**: - _"Creating subdomain documentation in [`.pair/adoption/product/subdomain/`](.pair/adoption/product/subdomain):_ + _"Creating subdomain documentation in [`.pair/adoption/product/subdomain/`](../../adoption/product/subdomain):_ - _Individual files: [subdomain-name].md for each subdomain_ - _README.md: Catalog index with links and descriptions_ - - _Format: Following [Documentation Standards](.pair/knowledge/guidelines/README.md)_ + - _Format: Following [Documentation Standards](../guidelines/README.md)_ _All files will be validated before storage. Ready to generate?"_ @@ -179,16 +179,16 @@ SUBDOMAIN DEFINITION STATE: ### Core Documentation -- [Product Requirements Document](.pair/adoption/product/PRD.md) - Business context and objectives -- [Strategic Initiatives](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - Business priorities and roadmap +- [Product Requirements Document](../../adoption/product/PRD.md) - Business context and objectives +- [Strategic Initiatives](../guidelines/collaboration/project-management-tool/README.md) - Business priorities and roadmap - [Bootstrap Checklist](02-how-to-complete-bootstrap-checklist.md) - Prerequisites and setup ### Guidelines Integration -- [Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md) - DDD implementation patterns -- [Strategic Subdomain Definition](.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md) - Comprehensive subdomain classification framework -- [Documentation Standards](.pair/knowledge/guidelines/README.md) - Format and structure requirements -- [Team Responsibilities](.pair/knowledge/guidelines/collaboration/team/role-responsibilities.md) - Subdomain definition roles +- [Domain-Driven Design](../guidelines/architecture/design-patterns/domain-driven-design.md) - DDD implementation patterns +- [Strategic Subdomain Definition](../guidelines/architecture/design-patterns/strategic-subdomain-definition.md) - Comprehensive subdomain classification framework +- [Documentation Standards](../guidelines/README.md) - Format and structure requirements +- [Team Responsibilities](../guidelines/collaboration/team/role-responsibilities.md) - Subdomain definition roles ### Next Phase diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md index 0918fef3..2bf316b4 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/05-how-to-define-bounded-contexts.md @@ -29,12 +29,12 @@ BOUNDED CONTEXT DEFINITION STATE: ### Strategic Context Architecture -- **Analyze subdomain foundation FIRST** - base contexts on validated [subdomain definitions](.pair/adoption/product/subdomain) -- **Apply DDD context mapping** - use [Bounded Context Patterns](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md) +- **Analyze subdomain foundation FIRST** - base contexts on validated [subdomain definitions](../../adoption/product/subdomain) +- **Apply DDD context mapping** - use [Bounded Context Patterns](../guidelines/architecture/design-patterns/bounded-contexts.md) - **Create catalog before details** - validate complete context landscape first, then define individually - **Design for team autonomy** - align contexts with team boundaries and deployment independence - **Map integration patterns** - identify all context relationships and anti-corruption layer needs -- **Follow adoption standards** - document per [Documentation Guidelines](.pair/knowledge/guidelines/README.md) +- **Follow adoption standards** - document per [Documentation Guidelines](../guidelines/README.md) **CRITICAL**: Before starting bounded context definition: @@ -51,49 +51,49 @@ BOUNDED CONTEXT DEFINITION STATE: 1. **Analyze Prerequisites**: - - Subdomain definitions: [`.pair/adoption/product/subdomain/`](.pair/adoption/product/subdomain) - - Technical architecture: [`.pair/adoption/tech/architecture.md`](.pair/adoption/tech/architecture.md) - - Technology stack: [`.pair/adoption/tech/tech-stack.md`](.pair/adoption/tech/tech-stack.md) - - Team structure: [`.pair/adoption/tech/way-of-working.md`](.pair/adoption/tech/way-of-working.md) + - Subdomain definitions: [`.pair/adoption/product/subdomain/`](../../adoption/product/subdomain) + - Technical architecture: [`.pair/adoption/tech/architecture.md`](../../adoption/tech/architecture.md) + - Technology stack: [`.pair/adoption/tech/tech-stack.md`](../../adoption/tech/tech-stack.md) + - Team structure: [`.pair/adoption/tech/way-of-working.md`](../../adoption/tech/way-of-working.md) 2. **Extract Context Indicators from Adoption Files**: - **From PRD** ([`.pair/adoption/product/PRD.md`](.pair/adoption/product/PRD.md)): + **From PRD** ([`.pair/adoption/product/PRD.md`](../../adoption/product/PRD.md)): - User personas and workflows that suggest UI context boundaries - Business capabilities that require different data consistency models - Success metrics that indicate separate measurement contexts - Integration requirements with external systems - **From Architecture** ([`.pair/adoption/tech/architecture.md`](.pair/adoption/tech/architecture.md)): + **From Architecture** ([`.pair/adoption/tech/architecture.md`](../../adoption/tech/architecture.md)): - Service decomposition patterns (microservices vs modular monolith) - Data consistency requirements (strong vs eventual consistency) - Performance requirements that drive service boundaries - Security boundaries and compliance requirements - **From Tech Stack** ([`.pair/adoption/tech/tech-stack.md`](.pair/adoption/tech/tech-stack.md)): + **From Tech Stack** ([`.pair/adoption/tech/tech-stack.md`](../../adoption/tech/tech-stack.md)): - Technology constraints that influence service separation - Database choices that impact data ownership boundaries - Communication protocols available for integration patterns - Deployment unit preferences (containers, serverless, etc.) - **From Infrastructure** ([`.pair/adoption/tech/infrastructure.md`](.pair/adoption/tech/infrastructure.md)): + **From Infrastructure** ([`.pair/adoption/tech/infrastructure.md`](../../adoption/tech/infrastructure.md)): - Deployment boundaries and scaling requirements - Network topology that influences service communication - Security zones that require context isolation - Operational monitoring and observability needs - **From UX/UI** ([`.pair/adoption/tech/ux-ui.md`](.pair/adoption/tech/ux-ui.md)): + **From UX/UI** ([`.pair/adoption/tech/ux-ui.md`](../../adoption/tech/ux-ui.md)): - User journey boundaries that suggest frontend context separation - Design system components that indicate shared UI contexts - Device-specific requirements that drive context boundaries - Accessibility requirements that influence service design - **From Way of Working** ([`.pair/adoption/tech/way-of-working.md`](.pair/adoption/tech/way-of-working.md)): + **From Way of Working** ([`.pair/adoption/tech/way-of-working.md`](../../adoption/tech/way-of-working.md)): - Team structure and ownership that drives context boundaries - Development velocity requirements for independent deployment @@ -104,15 +104,15 @@ BOUNDED CONTEXT DEFINITION STATE: _"I need to verify context definition prerequisites using adoption files:_ - - _**PRD Analysis** ([PRD.md](.pair/adoption/product/PRD.md)): [business capabilities and user workflows identified]_ - - _**Architecture Decisions** ([architecture.md](.pair/adoption/tech/architecture.md)): [service patterns and consistency models defined]_ - - _**Technology Stack** ([tech-stack.md](.pair/adoption/tech/tech-stack.md)): [integration capabilities and deployment constraints]_ - - _**Infrastructure Setup** ([infrastructure.md](.pair/adoption/tech/infrastructure.md)): [deployment boundaries and scaling patterns]_ - - _**Team Structure** ([way-of-working.md](.pair/adoption/tech/way-of-working.md)): [ownership model and communication patterns]_ + - _**PRD Analysis** ([PRD.md](../../adoption/product/PRD.md)): [business capabilities and user workflows identified]_ + - _**Architecture Decisions** ([architecture.md](../../adoption/tech/architecture.md)): [service patterns and consistency models defined]_ + - _**Technology Stack** ([tech-stack.md](../../adoption/tech/tech-stack.md)): [integration capabilities and deployment constraints]_ + - _**Infrastructure Setup** ([infrastructure.md](../../adoption/tech/infrastructure.md)): [deployment boundaries and scaling patterns]_ + - _**Team Structure** ([way-of-working.md](../../adoption/tech/way-of-working.md)): [ownership model and communication patterns]_ _Missing or incomplete: [specific adoption files]. Should we complete [missing decisions] first or proceed with available constraints?"_ -**Context Boundary Synthesis**: Combine insights from all adoption files using [Context Identification Criteria](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#context-identification) +**Context Boundary Synthesis**: Combine insights from all adoption files using [Context Identification Criteria](../guidelines/architecture/design-patterns/bounded-contexts.md#context-identification) **Foundation Reference**: [Subdomain Definition](04-how-to-define-subdomains.md) @@ -124,17 +124,17 @@ BOUNDED CONTEXT DEFINITION STATE: **Apply Adoption Constraints from Technical Decisions**: - - **Architecture patterns** from [architecture.md](.pair/adoption/tech/architecture.md): microservices vs modular monolith influences context granularity - - **Technology stack** from [tech-stack.md](.pair/adoption/tech/tech-stack.md): database choices determine data ownership boundaries - - **Infrastructure constraints** from [infrastructure.md](.pair/adoption/tech/infrastructure.md): deployment units and scaling requirements - - **Team boundaries** from [way-of-working.md](.pair/adoption/tech/way-of-working.md): ownership model drives context responsibility + - **Architecture patterns** from [architecture.md](../../adoption/tech/architecture.md): microservices vs modular monolith influences context granularity + - **Technology stack** from [tech-stack.md](../../adoption/tech/tech-stack.md): database choices determine data ownership boundaries + - **Infrastructure constraints** from [infrastructure.md](../../adoption/tech/infrastructure.md): deployment units and scaling requirements + - **Team boundaries** from [way-of-working.md](../../adoption/tech/way-of-working.md): ownership model drives context responsibility **Business Context Analysis**: - - **PRD capabilities** from [PRD.md](.pair/adoption/product/PRD.md): user journeys and business processes that require isolation - - **UX boundaries** from [ux-ui.md](.pair/adoption/tech/ux-ui.md): frontend context separation based on user interface patterns + - **PRD capabilities** from [PRD.md](../../adoption/product/PRD.md): user journeys and business processes that require isolation + - **UX boundaries** from [ux-ui.md](../../adoption/tech/ux-ui.md): frontend context separation based on user interface patterns - **Subdomain groupings** that align with technical and organizational constraints - - Use [Context Boundaries criteria](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#context-boundaries) to validate technical and business alignment + - Use [Context Boundaries criteria](../guidelines/architecture/design-patterns/bounded-contexts.md#context-boundaries) to validate technical and business alignment 2. **Context Catalog Proposal**: @@ -182,7 +182,7 @@ BOUNDED CONTEXT DEFINITION STATE: - _Merge/Split: [Boundary adjustments with reasons]_ - _Reassign: [Subdomain moves with justification]_ - _Updated integration patterns (using [Integration Patterns](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#integration-patterns)):_ + _Updated integration patterns (using [Integration Patterns](../guidelines/architecture/design-patterns/bounded-contexts.md#integration-patterns)):_ - _Partnership: [cooperative contexts] with coordinated evolution_ - _Customer-Supplier: [upstream] → [downstream] with negotiated interfaces_ @@ -190,7 +190,7 @@ BOUNDED CONTEXT DEFINITION STATE: _Is this the final context catalog for detailed definition?"_ -**Context Mapping Reference**: [Bounded Context Patterns](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md) +**Context Mapping Reference**: [Bounded Context Patterns](../guidelines/architecture/design-patterns/bounded-contexts.md) ### Phase 3: Context Validation & Documentation @@ -208,14 +208,14 @@ BOUNDED CONTEXT DEFINITION STATE: **Team Ownership**: [Responsible team and autonomy level] **Service Boundaries**: [Internal services and public interfaces] **Data Ownership**: [Key aggregates and consistency requirements] - **Integration Patterns**: [Dependencies and provided services using specific patterns from [Context Communication](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#context-communication)] - **Ubiquitous Language**: [Context-specific terminology and dialect per [Language Guidelines](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#ubiquitous-language)] + **Integration Patterns**: [Dependencies and provided services using specific patterns from [Context Communication](../guidelines/architecture/design-patterns/bounded-contexts.md#context-communication)] + **Ubiquitous Language**: [Context-specific terminology and dialect per [Language Guidelines](../guidelines/architecture/design-patterns/bounded-contexts.md#ubiquitous-language)] **Quality Attributes**: [Performance, scalability, reliability needs] ``` 2. **Integration Architecture Validation**: - _"Complete integration architecture for validation (following [Integration Patterns](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#integration-patterns)):_ + _"Complete integration architecture for validation (following [Integration Patterns](../guidelines/architecture/design-patterns/bounded-contexts.md#integration-patterns)):_ **Synchronous Integrations** ([X] total): @@ -229,7 +229,7 @@ BOUNDED CONTEXT DEFINITION STATE: - _[Context] ↔ [External]: [ACL Protection strategy] - [risk mitigation]_ - **Context Map** (per [Context Maps Guidelines](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#context-maps)): + **Context Map** (per [Context Maps Guidelines](../guidelines/architecture/design-patterns/bounded-contexts.md#context-maps)): - _Upstream/Downstream relationships documented_ - _Integration patterns specified for each connection_ @@ -243,12 +243,12 @@ BOUNDED CONTEXT DEFINITION STATE: 1. **Document Generation**: - _"Creating bounded context documentation in [`.pair/adoption/tech/boundedcontext/`](.pair/adoption/tech/boundedcontext):_ + _"Creating bounded context documentation in [`.pair/adoption/tech/boundedcontext/`](../../adoption/tech/boundedcontext):_ - _Individual files: [context-name].md for each context_ - - _README.md: Context catalog with integration overview and [Context Map](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#context-maps)_ - - _Format: Following [Documentation Standards](.pair/knowledge/guidelines/README.md)_ - - _Integration patterns documented per [Implementation Strategies](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md#implementation-strategies)_ + - _README.md: Context catalog with integration overview and [Context Map](../guidelines/architecture/design-patterns/bounded-contexts.md#context-maps)_ + - _Format: Following [Documentation Standards](../guidelines/README.md)_ + - _Integration patterns documented per [Implementation Strategies](../guidelines/architecture/design-patterns/bounded-contexts.md#implementation-strategies)_ _All files validated and ready for storage. Proceed with generation?"_ @@ -283,15 +283,15 @@ BOUNDED CONTEXT DEFINITION STATE: ### Core Dependencies - [Subdomain Definition](04-how-to-define-subdomains.md) - Business context foundation -- [Technical Architecture](.pair/adoption/tech/architecture.md) - Integration constraints and patterns -- [Team Structure](.pair/adoption/tech/way-of-working.md) - Organizational boundaries and capabilities +- [Technical Architecture](../../adoption/tech/architecture.md) - Integration constraints and patterns +- [Team Structure](../../adoption/tech/way-of-working.md) - Organizational boundaries and capabilities ### Implementation Guidelines -- [Bounded Context Patterns](.pair/knowledge/guidelines/architecture/design-patterns/bounded-contexts.md) - Context identification and implementation strategies -- [Domain-Driven Design](.pair/knowledge/guidelines/architecture/design-patterns/domain-driven-design.md) - DDD implementation patterns -- [Strategic Subdomain Definition](.pair/knowledge/guidelines/architecture/design-patterns/strategic-subdomain-definition.md) - Context boundary strategies -- [Documentation Standards](.pair/knowledge/guidelines/README.md) - Format and structure requirements +- [Bounded Context Patterns](../guidelines/architecture/design-patterns/bounded-contexts.md) - Context identification and implementation strategies +- [Domain-Driven Design](../guidelines/architecture/design-patterns/domain-driven-design.md) - DDD implementation patterns +- [Strategic Subdomain Definition](../guidelines/architecture/design-patterns/strategic-subdomain-definition.md) - Context boundary strategies +- [Documentation Standards](../guidelines/README.md) - Format and structure requirements ### Next Phase diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/06-how-to-breakdown-epics.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/06-how-to-breakdown-epics.md index 3d954bbd..a0cbf6cd 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/06-how-to-breakdown-epics.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/06-how-to-breakdown-epics.md @@ -35,12 +35,12 @@ EPIC BREAKDOWN STATE: - **Size for 2-4 sprints** - manageable increments with measurable outcomes - **Plan Epic 0 for new projects** - application bootstrap and technical foundation - **Follow collaborative validation** - structured feedback loops with developer approval -- **Document comprehensively** - use [Epic Template](.pair/knowledge/guidelines/collaboration/templates/epic-template.md) -- **Maintain tool integration** - proper hierarchy linking per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +- **Document comprehensively** - use [Epic Template](../guidelines/collaboration/templates/epic-template.md) +- **Maintain tool integration** - proper hierarchy linking per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) **CRITICAL**: Before starting epic breakdown: -- **HALT if bootstrap incomplete** - verify [way-of-working.md](.pair/adoption/tech/way-of-working.md) and tool configuration +- **HALT if bootstrap incomplete** - verify [way-of-working.md](../../adoption/tech/way-of-working.md) and tool configuration - **HALT if no Todo initiatives** - initiatives must be ready for breakdown - **HALT if tool access unclear** - must understand PM tool hierarchy and linking approach - **Do NOT proceed** without clear initiative selection and technical context @@ -53,9 +53,9 @@ EPIC BREAKDOWN STATE: 1. **Verify Bootstrap Completion**: - - Confirm [way-of-working.md](.pair/adoption/tech/way-of-working.md) exists with PM tool configuration + - Confirm [way-of-working.md](../../adoption/tech/way-of-working.md) exists with PM tool configuration - Check foundational documents: PRD, architecture, tech-stack, boundedcontext - - Validate PM tool access per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) + - Validate PM tool access per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) 2. **Handle Missing Prerequisites**: @@ -90,7 +90,7 @@ EPIC BREAKDOWN STATE: _This initiative will deliver [key user value]. Should I proceed with epic breakdown for this initiative?"_ -**Selection Reference**: [Initiative Guidelines](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) +**Selection Reference**: [Initiative Guidelines](../guidelines/collaboration/templates/initiative-template.md) ### Phase 3: Epic Analysis & Proposal @@ -125,7 +125,7 @@ EPIC BREAKDOWN STATE: _Does this breakdown structure align with your development approach and initiative objectives?"_ -**Epic Sizing Reference**: [Epic Template](.pair/knowledge/guidelines/collaboration/templates/epic-template.md) +**Epic Sizing Reference**: [Epic Template](../guidelines/collaboration/templates/epic-template.md) ### Phase 4: Epic Documentation & Creation @@ -133,7 +133,7 @@ EPIC BREAKDOWN STATE: 1. **Document Individual Epics**: - - Use complete [Epic Template](.pair/knowledge/guidelines/collaboration/templates/epic-template.md) structure + - Use complete [Epic Template](../guidelines/collaboration/templates/epic-template.md) structure - Start with Epic 0 (if required), then sequential order - Include objective, scope, success criteria, technical considerations - Define clear user value and business rationale @@ -151,12 +151,12 @@ EPIC BREAKDOWN STATE: _Does this epic definition capture the right scope and value delivery? Any adjustments needed?"_ 3. **Create in Project Management Tool**: - - Follow tool-specific format per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) + - Follow tool-specific format per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - Establish proper hierarchy linking (Initiative → Epic → Future User Stories) - Configure epic tracking and progress monitoring - Verify epic sequence and dependencies are documented -**Documentation Reference**: [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +**Documentation Reference**: [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) ### Phase 5: Completion & State Management @@ -191,8 +191,8 @@ EPIC BREAKDOWN STATE: - [ ] Epic 0 assessed for new projects (created if needed) - [ ] All epics deliver end-to-end user value in 2-4 sprints - [ ] Epic sequence follows logical dependencies (foundation → user value) -- [ ] Complete [Epic Template](.pair/knowledge/guidelines/collaboration/templates/epic-template.md) used for each epic -- [ ] Tool hierarchy properly established per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +- [ ] Complete [Epic Template](../guidelines/collaboration/templates/epic-template.md) used for each epic +- [ ] Tool hierarchy properly established per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - [ ] Initiative status updated from 'Todo' to 'In Progress' - [ ] Session state maintained throughout process @@ -202,12 +202,12 @@ EPIC BREAKDOWN STATE: - [Bootstrap Checklist](02-how-to-complete-bootstrap-checklist.md) - Foundation verification - [Initiative Creation](03-how-to-create-and-prioritize-initiatives.md) - Input source for epic breakdown -- [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - Tool integration and hierarchy linking +- [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - Tool integration and hierarchy linking ### Implementation Guidelines -- [Epic Template](.pair/knowledge/guidelines/collaboration/templates/epic-template.md) - Complete documentation structure -- [Initiative Template](.pair/knowledge/guidelines/collaboration/templates/initiative-template.md) - Parent context understanding +- [Epic Template](../guidelines/collaboration/templates/epic-template.md) - Complete documentation structure +- [Initiative Template](../guidelines/collaboration/templates/initiative-template.md) - Parent context understanding ### Next Phase diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md index 0cae98eb..cd2012af 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/07-how-to-breakdown-user-stories.md @@ -30,19 +30,19 @@ USER STORY BREAKDOWN STATE: ### Strategic Story Architecture - **Verify epic readiness FIRST** - epic must be completed and ready for breakdown -- **Apply INVEST criteria** - follow [User Story Guidelines](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) +- **Apply INVEST criteria** - follow [User Story Guidelines](../guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) - **Use vertical slicing** - each story delivers end-to-end user value with UI manifestation - **Size for single sprint** - rough estimates with expected uncertainty - **Focus on UI-first cutting** - every story produces visible, demonstrable value -- **Follow tool integration** - proper hierarchy linking per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +- **Follow tool integration** - proper hierarchy linking per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - **Maintain epic coverage** - ensure all epic scope addressed by stories -- **Document with templates** - use [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) +- **Document with templates** - use [User Story Template](../guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) **CRITICAL**: Before starting user story breakdown: - **HALT if epic incomplete** - epic must be fully documented and ready - **HALT if tool access unclear** - must understand PM tool hierarchy and linking -- **HALT if bootstrap incomplete** - verify [way-of-working.md](.pair/adoption/tech/way-of-working.md) configuration +- **HALT if bootstrap incomplete** - verify [way-of-working.md](../../adoption/tech/way-of-working.md) configuration - **Do NOT proceed** without clear epic context and tool setup ## Implementation Workflow @@ -53,8 +53,8 @@ USER STORY BREAKDOWN STATE: 1. **Verify Tool Configuration**: - - Check [way-of-working.md](.pair/adoption/tech/way-of-working.md) for PM tool setup - - Validate access per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) + - Check [way-of-working.md](../../adoption/tech/way-of-working.md) for PM tool setup + - Validate access per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - Confirm hierarchy linking methodology (Epic → User Story) 2. **Handle Missing Configuration**: @@ -130,7 +130,7 @@ USER STORY BREAKDOWN STATE: _Does this story identification capture the right user value breakdown and UI manifestations?"_ -**Story Patterns Reference**: [Vertical Slicing Guidelines](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) +**Story Patterns Reference**: [Vertical Slicing Guidelines](../guidelines/collaboration/templates/user-story-template.md) ### Phase 4: Story Definition & INVEST Validation @@ -170,7 +170,7 @@ USER STORY BREAKDOWN STATE: _This breakdown provides rough planning units with expected uncertainty. Approved for documentation?"_ -**INVEST Reference**: [INVEST Criteria Guidelines](.pair/knowledge/guidelines/collaboration/methodology/scrum.md) +**INVEST Reference**: [INVEST Criteria Guidelines](../guidelines/collaboration/methodology/scrum.md) ### Phase 5: Documentation & Tool Creation @@ -178,7 +178,7 @@ USER STORY BREAKDOWN STATE: 1. **Document Individual Stories**: - - Use complete [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) + - Use complete [User Story Template](../guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) - Focus on planning essentials (statement, value, scope, sizing) - Include UI value manifestation for demo readiness - Document uncertainties for future refinement @@ -195,12 +195,12 @@ USER STORY BREAKDOWN STATE: _Does this story definition provide sufficient planning information while acknowledging expected uncertainties?"_ 3. **Create in Project Management Tool**: - - Follow tool-specific format per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) + - Follow tool-specific format per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - Establish proper hierarchy linking (Epic → User Story) - Configure basic tracking (status, priority, sizing) - Verify story sequence and dependencies -**Template Reference**: [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) +**Template Reference**: [User Story Template](../guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) ### Phase 6: Coverage Validation & Completion @@ -234,8 +234,8 @@ USER STORY BREAKDOWN STATE: - [ ] Story identification using patterns and epic context - [ ] All stories follow INVEST criteria validation - [ ] UI-first cutting applied - every story produces visible value -- [ ] Complete [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) used -- [ ] Tool hierarchy properly established per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +- [ ] Complete [User Story Template](../guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) used +- [ ] Tool hierarchy properly established per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - [ ] Epic coverage validated and status updated - [ ] Session state maintained throughout process @@ -293,14 +293,14 @@ USER STORY BREAKDOWN STATE: ### Core Dependencies - [Epic Breakdown](06-how-to-breakdown-epics.md) - Input source for user story breakdown -- [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - Tool integration and hierarchy linking +- [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - Tool integration and hierarchy linking - [Bootstrap Checklist](02-how-to-complete-bootstrap-checklist.md) - Foundation verification ### Implementation Guidelines -- [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) - Complete documentation structure -- [INVEST Criteria Guidelines](.pair/knowledge/guidelines/collaboration/methodology/scrum.md) - Story validation framework -- [Vertical Slicing Guidelines](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) - Story cutting patterns +- [User Story Template](../guidelines/collaboration/templates/user-story-template.md#initial-breakdown-template) - Complete documentation structure +- [INVEST Criteria Guidelines](../guidelines/collaboration/methodology/scrum.md) - Story validation framework +- [Vertical Slicing Guidelines](../guidelines/collaboration/templates/user-story-template.md) - Story cutting patterns ### Next Phase diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/08-how-to-refine-a-user-story.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/08-how-to-refine-a-user-story.md index 08eab5fe..669cdfe0 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/08-how-to-refine-a-user-story.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/08-how-to-refine-a-user-story.md @@ -31,16 +31,16 @@ STORY REFINEMENT STATE: - **Select highest priority Todo stories** - follow P0 > P1 > P2 priority order - **Transform uncertainty into clarity** - resolve all open questions and ambiguities -- **Apply comprehensive acceptance criteria** - use Given-When-Then format per [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) +- **Apply comprehensive acceptance criteria** - use Given-When-Then format per [User Story Template](../guidelines/collaboration/templates/user-story-template.md) - **Conduct technical risk analysis** - identify implementation challenges and spikes - **Validate sprint readiness** - ensure story fits capacity or split appropriately - **Maintain INVEST compliance** - verify all INVEST criteria remain satisfied -- **Document with refined template** - complete all sections of [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) +- **Document with refined template** - complete all sections of [User Story Template](../guidelines/collaboration/templates/user-story-template.md) **CRITICAL**: Before starting story refinement: - **HALT if no Todo stories** - must have stories from breakdown phase -- **HALT if tool access unclear** - verify PM tool configuration per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +- **HALT if tool access unclear** - verify PM tool configuration per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - **HALT if template not reviewed** - must understand refined story structure - **Do NOT proceed** without clear story selection and template understanding @@ -98,7 +98,7 @@ STORY REFINEMENT STATE: _Based on your input, I'll create comprehensive Given-When-Then acceptance criteria."_ -**Requirements Reference**: [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) +**Requirements Reference**: [User Story Template](../guidelines/collaboration/templates/user-story-template.md) ### Phase 3: Technical Analysis @@ -136,7 +136,7 @@ STORY REFINEMENT STATE: _Does this technical approach align with project architecture and team capabilities?"_ -**Technical Reference**: [Architecture Guidelines](.pair/knowledge/guidelines/architecture/architectural-patterns/README.md) +**Technical Reference**: [Architecture Guidelines](../guidelines/architecture/architectural-patterns/README.md) ### Phase 4: Sprint Readiness Validation @@ -172,7 +172,7 @@ STORY REFINEMENT STATE: _Does this sizing and potential splitting preserve user value appropriately?"_ -**Sizing Reference**: [Story Estimation Guidelines](.pair/knowledge/guidelines/collaboration/estimation/README.md) +**Sizing Reference**: [Story Estimation Guidelines](../guidelines/collaboration/estimation/README.md) ### Phase 5: Documentation and Tool Updates @@ -180,7 +180,7 @@ STORY REFINEMENT STATE: 1. **Template Documentation**: - - Complete all sections of [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) + - Complete all sections of [User Story Template](../guidelines/collaboration/templates/user-story-template.md) - Include detailed acceptance criteria and technical analysis - Document dependencies, risks, and implementation notes - Specify Definition of Done checklist items @@ -203,7 +203,7 @@ STORY REFINEMENT STATE: _Story refinement complete. All details documented and ready for sprint execution."_ -**Template Reference**: [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) +**Template Reference**: [User Story Template](../guidelines/collaboration/templates/user-story-template.md) ## Quality Assurance @@ -214,7 +214,7 @@ STORY REFINEMENT STATE: - [ ] Technical approach and risks thoroughly analyzed - [ ] Story sized appropriately for sprint or split with value preservation - [ ] All uncertainties and open questions resolved -- [ ] [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) completed +- [ ] [User Story Template](../guidelines/collaboration/templates/user-story-template.md) completed - [ ] Tool updated with refined status and metadata - [ ] Story ready for immediate development start @@ -272,14 +272,14 @@ STORY REFINEMENT STATE: ### Core Dependencies - [User Story Breakdown](07-how-to-breakdown-user-stories.md) - Input source for refinement candidates -- [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - Tool access and story management +- [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - Tool access and story management - [Bootstrap Checklist](02-how-to-complete-bootstrap-checklist.md) - Foundation verification ### Implementation Guidelines -- [User Story Template](.pair/knowledge/guidelines/collaboration/templates/user-story-template.md) - Complete documentation structure -- [Story Estimation Guidelines](.pair/knowledge/guidelines/collaboration/estimation/README.md) - Sizing and splitting standards -- [Architecture Guidelines](.pair/knowledge/guidelines/architecture/architectural-patterns/README.md) - Technical analysis framework +- [User Story Template](../guidelines/collaboration/templates/user-story-template.md) - Complete documentation structure +- [Story Estimation Guidelines](../guidelines/collaboration/estimation/README.md) - Sizing and splitting standards +- [Architecture Guidelines](../guidelines/architecture/architectural-patterns/README.md) - Technical analysis framework ### Next Phase diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/09-how-to-create-tasks.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/09-how-to-create-tasks.md index 9e273148..c7d97dd4 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/09-how-to-create-tasks.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/09-how-to-create-tasks.md @@ -32,19 +32,19 @@ TASK CREATION STATE: ### Strategic Task Architecture - **Verify story refinement FIRST** - story must be refined and ready for breakdown -- **Apply technical standards** - follow [Adoption Guidelines](.pair/adoption/tech) consistently +- **Apply technical standards** - follow [Adoption Guidelines](../../adoption/tech) consistently - **Use bounded context mapping** - each task specifies its implementation domain - **Size for implementation clarity** - clear guidance without architectural decisions - **Focus on executable steps** - every task produces demonstrable progress -- **Follow tool integration** - proper hierarchy linking per [PM Tool Guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) +- **Follow tool integration** - proper hierarchy linking per [PM Tool Guidelines](../guidelines/collaboration/project-management-tool/README.md) - **Maintain story coverage** - ensure all acceptance criteria addressed by tasks -- **Document with templates** - use [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) +- **Document with templates** - use [Task Template](../guidelines/collaboration/templates/task-template.md) **CRITICAL**: Before starting task creation: - **HALT if story not refined** - story must be in 'Refined' state with clear acceptance criteria - **HALT if tool access unclear** - must understand PM tool hierarchy and linking -- **HALT if bounded context unknown** - verify [Bounded Context Documentation](.pair/adoption/tech/boundedcontext) +- **HALT if bounded context unknown** - verify [Bounded Context Documentation](../../adoption/tech/boundedcontext) - **Do NOT proceed** without clear story context and technical setup ## Implementation Workflow @@ -55,7 +55,7 @@ TASK CREATION STATE: 1. **Verify Tool Configuration**: - - Check [way-of-working.md](.pair/adoption/tech/way-of-working.md) for PM tool setup + - Check [way-of-working.md](../../adoption/tech/way-of-working.md) for PM tool setup - Confirm task creation and hierarchy linking methodology (Story → Task) 2. **Handle Missing Configuration**: @@ -92,14 +92,14 @@ TASK CREATION STATE: 1. **Review Technical Adoption**: - - **Architecture**: Check [architecture.md](.pair/adoption/tech/architecture.md) for patterns - - **Tech Stack**: Study [tech-stack.md](.pair/adoption/tech/tech-stack.md) for implementation choices - - **Infrastructure**: Review [infrastructure.md](.pair/adoption/tech/infrastructure.md) for deployment - - **UX/UI**: Examine [ux-ui.md](.pair/adoption/tech/ux-ui.md) for interface standards + - **Architecture**: Check [architecture.md](../../adoption/tech/architecture.md) for patterns + - **Tech Stack**: Study [tech-stack.md](../../adoption/tech/tech-stack.md) for implementation choices + - **Infrastructure**: Review [infrastructure.md](../../adoption/tech/infrastructure.md) for deployment + - **UX/UI**: Examine [ux-ui.md](../../adoption/tech/ux-ui.md) for interface standards 2. **Identify Bounded Context**: - - Map story to [Bounded Context](.pair/adoption/tech/boundedcontext) documentation + - Map story to [Bounded Context](../../adoption/tech/boundedcontext) documentation - Determine implementation scope and affected modules - Identify integration points and dependencies @@ -115,7 +115,7 @@ TASK CREATION STATE: Ready to proceed with task identification?" ``` -**Context Reference**: [Bounded Context Guidelines](.pair/knowledge/guidelines/architecture/README.md) +**Context Reference**: [Bounded Context Guidelines](../guidelines/architecture/README.md) ### Phase 4: Task Identification & Decomposition @@ -130,9 +130,9 @@ TASK CREATION STATE: 2. **Apply Technical Layer Analysis**: - - Reference [Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md) - - Follow [Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) - - Apply [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) + - Reference [Code Design Guidelines](../guidelines/code-design/README.md) + - Follow [Testing Strategy](../guidelines/testing/test-strategy/README.md) + - Apply [Security Guidelines](../guidelines/quality-assurance/security/README.md) 3. **Present Task Breakdown**: @@ -147,7 +147,7 @@ TASK CREATION STATE: Approved for detailed task definition?" ``` -**Decomposition Reference**: [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) +**Decomposition Reference**: [Task Template](../guidelines/collaboration/templates/task-template.md) ### Phase 5: Task Definition & Technical Specification @@ -162,9 +162,9 @@ TASK CREATION STATE: 2. **Apply Technical Standards**: - - **Architecture**: Reference [Architecture Guidelines](.pair/knowledge/guidelines/architecture/README.md) - - **Implementation**: Link [Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md) - - **Quality**: Apply [Definition of Done](.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md) + - **Architecture**: Reference [Architecture Guidelines](../guidelines/architecture/README.md) + - **Implementation**: Link [Technical Standards](../guidelines/technical-standards/README.md) + - **Quality**: Apply [Definition of Done](../guidelines/quality-assurance/quality-standards/definition-of-done.md) 3. **Handle Non-Standard Solutions**: ``` @@ -174,7 +174,7 @@ TASK CREATION STATE: Should I proceed with standard approach or propose alternative with ADR?" ``` -**Standards Reference**: [Guidelines Overview](.pair/knowledge/guidelines/README.md) +**Standards Reference**: [Guidelines Overview](../guidelines/README.md) ### Phase 6: Documentation & Tool Creation @@ -185,7 +185,7 @@ TASK CREATION STATE: Create a task breakdown section with: - Checkbox list of all tasks with IDs and titles (for status tracking) - - Detailed documentation for each task following [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) + - Detailed documentation for each task following [Task Template](../guidelines/collaboration/templates/task-template.md) 2. **Append to Story Body**: @@ -197,11 +197,11 @@ TASK CREATION STATE: 3. **Template Compliance**: - - Follow [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) structure precisely + - Follow [Task Template](../guidelines/collaboration/templates/task-template.md) structure precisely - Include: bounded context, technical standards, module specifications - Reference specific guideline sections for implementation -**Template Reference**: [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) +**Template Reference**: [Task Template](../guidelines/collaboration/templates/task-template.md) ### Phase 7: Coverage Validation & Completion @@ -319,26 +319,26 @@ TASK CREATION STATE: ### 🏗️ Architecture & Design -- **[Architecture Guidelines](.pair/knowledge/guidelines/architecture/README.md)** - System architecture patterns, bounded contexts, and ADR processes -- **[Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md)** - Code organization, design patterns, and implementation standards +- **[Architecture Guidelines](../guidelines/architecture/README.md)** - System architecture patterns, bounded contexts, and ADR processes +- **[Code Design Guidelines](../guidelines/code-design/README.md)** - Code organization, design patterns, and implementation standards ### ⚙️ Technical Implementation -- **[Technical Standards](.pair/knowledge/guidelines/technical-standards/README.md)** - Tech stack, development tools, and feature flag management -- **[Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md)** - Deployment strategies, environment management, and CI/CD +- **[Technical Standards](../guidelines/technical-standards/README.md)** - Tech stack, development tools, and feature flag management +- **[Infrastructure Guidelines](../guidelines/infrastructure/README.md)** - Deployment strategies, environment management, and CI/CD ### 🎨 User Experience & Quality -- **[User Experience Guidelines](.pair/knowledge/guidelines/user-experience/README.md)** - User experience standards and design principles -- **[Definition of Done](.pair/knowledge/guidelines/quality-assurance/quality-standards/definition-of-done.md)** - Quality criteria and completion standards -- **[Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md)** - Testing frameworks, strategies, and quality gates +- **[User Experience Guidelines](../guidelines/user-experience/README.md)** - User experience standards and design principles +- **[Definition of Done](../guidelines/quality-assurance/quality-standards/definition-of-done.md)** - Quality criteria and completion standards +- **[Testing Strategy](../guidelines/testing/test-strategy/README.md)** - Testing frameworks, strategies, and quality gates ### 🔒 Security & Performance -- **[Accessibility Guidelines](.pair/knowledge/guidelines/quality-assurance/accessibility/README.md)** - Accessibility standards and compliance requirements -- **[Performance Guidelines](.pair/knowledge/guidelines/quality-assurance/performance/README.md)** - Performance optimization and monitoring strategies -- **[Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md)** - Security implementation and best practices -- **[Observability Guidelines](.pair/knowledge/guidelines/observability/README.md)** - Monitoring, logging, and tracing strategies +- **[Accessibility Guidelines](../guidelines/quality-assurance/accessibility/README.md)** - Accessibility standards and compliance requirements +- **[Performance Guidelines](../guidelines/quality-assurance/performance/README.md)** - Performance optimization and monitoring strategies +- **[Security Guidelines](../guidelines/quality-assurance/security/README.md)** - Security implementation and best practices +- **[Observability Guidelines](../guidelines/observability/README.md)** - Monitoring, logging, and tracing strategies **Process Dependencies:** diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/10-how-to-implement-a-task.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/10-how-to-implement-a-task.md index 1c11df58..e072d3c8 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/10-how-to-implement-a-task.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/10-how-to-implement-a-task.md @@ -5,7 +5,8 @@ Transform task specifications into working, tested code by implementing **exactly what is defined** in task breakdown without additions or modifications. **Role**: Product Software Engineer (Implementation) -**Process**: 🤖🤝👨‍💻 (AI implements, Developer reviews) +**Process**: AI implements, Developer reviews +**Skill**: When `/implement` is available, invoke it — it automates the operational steps of this workflow (branch creation, task iteration, commits, PR creation). This how-to describes the workflow and its HALT conditions. **CRITICAL FIRST STEP**: Before any implementation work begins, complete Phase 0: Story & Task Analysis to fully understand what needs to be implemented. @@ -29,427 +30,150 @@ IMPLEMENTATION STATE: ### Task-First Implementation -- **Implement ONLY** what is specified in the active task you find in the PM tool according to the [task template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) -- **No arbitrary additions** - if something seems missing, request task updates -- **Follow task specifications** for libraries, files, and implementation approach -- **Use ONLY specified libraries** - never add libraries not listed in task implementation approach +- **Implement ONLY** what is specified in the active task per the [task template](../guidelines/collaboration/templates/task-template.md) +- **No arbitrary additions** — if something seems missing, HALT and request task updates +- **Use ONLY specified libraries** — never add libraries not listed in [tech-stack.md](../../adoption/tech/tech-stack.md) or the task specification - **Validate against task acceptance criteria** before considering complete -**CRITICAL**: If task seems incomplete or requires additional libraries/changes: +### Technical Alignment -- **HALT implementation immediately** -- **Propose specific task updates** to developer -- **Suggest alternative approaches** based on [tech-stack.md](.pair/adoption/tech/tech-stack.md) -- **Do NOT proceed** until task is updated and complete +- **Architecture**: Follow [adopted architecture](../../adoption/tech/architecture.md) +- **Technology Stack**: Use ONLY libraries/versions from [tech-stack.md](../../adoption/tech/tech-stack.md) +- **Development Process**: Follow [way-of-working.md](../../adoption/tech/way-of-working.md) +- **Code Design**: Apply [code design guidelines](../guidelines/code-design/README.md) +- **Testing**: Follow [test strategy](../guidelines/testing/test-strategy/README.md) -### Technical Alignment Requirements +## Prerequisites & HALT Conditions -- **Architecture**: Follow patterns defined in [adopted architecture](.pair/adoption/tech/architecture.md) -- **Technology Stack**: Use ONLY libraries/versions from [tech-stack.md](.pair/adoption/tech/tech-stack.md) -- **Development Process**: Follow workflows from [way-of-working.md](.pair/adoption/tech/way-of-working.md) -- **Code Design**: Apply principles from [code design guidelines](.pair/knowledge/guidelines/code-design/README.md) -- **Testing**: Follow [test strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) for TDD implementation +### Critical Blockers (HALT if not met) -## Prerequisites & Guardrails - -### 🚫 Critical Blockers - -- **Clean Git**: No uncommitted changes, on main branch -- **PM Tool Configured**: Must exist in [way-of-working.md](.pair/adoption/tech/way-of-working.md) +- **Clean Git**: No uncommitted changes, on main branch (before starting) +- **PM Tool Configured**: Must exist in [way-of-working.md](../../adoption/tech/way-of-working.md) - **Story Analysis Complete**: Phase 0 must be completed before any other work +- **Story in "In Progress" state** and assigned to the implementing developer +- **All tasks complete** per [task template](../guidelines/collaboration/templates/task-template.md) — every task must have implementation approach, acceptance criteria, and development workflow +- **Libraries clear** — no ambiguity about which libraries to use -### 📋 Access Requirements - -Follow [project management tool guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) for tool-specific access procedures based on the configured tool in [way-of-working.md](.pair/adoption/tech/way-of-working.md). - -**Access Rules:** +### Access Requirements -- **✅ PERMITTED**: Filesystem access ONLY when tool = "filesystem" in way-of-working.md -- **🚫 PROHIBITED**: Filesystem access when any other tool is configured - -**IMPORTANT**: Before proceeding to any implementation phases, **Phase 0: Story & Task Analysis** must be completed successfully. This includes reading the complete user story, understanding all tasks, and confirming implementation readiness. +Follow [project management tool guidelines](../guidelines/collaboration/project-management-tool/README.md) for tool-specific access based on the configured tool in [way-of-working.md](../../adoption/tech/way-of-working.md). ## Implementation Methodology ### Task Type Classification -Based on [task template](.pair/knowledge/guidelines/collaboration/templates/task-template.md), determine implementation approach: - -**Development Tasks (TDD Required):** - -- **Feature Implementation** - New functionality development -- **Bug Fix** - Correcting identified issues or defects -- **Refactoring** - Code improvement without behavior changes -- **Testing** - Test creation, execution, or automation +Based on [task template](../guidelines/collaboration/templates/task-template.md): -**Non-Development Tasks (Direct Implementation):** +**Development Tasks (TDD Required):** Feature implementation, Bug fix, Refactoring, Testing -- **Documentation** - Creating or updating documentation -- **Configuration** - Setup, deployment, or environment tasks -- **Research** - Investigation, spike, or proof of concept +**Non-Development Tasks (Direct Implementation):** Documentation, Configuration, Research -### TDD Implementation Methodology (Development Tasks Only) +### TDD Session Management (Development Tasks Only) -**CRITICAL: Test-Driven Development Rules** +Follow [TDD guidelines](../guidelines/testing/test-strategy/tdd-test-driven-development.md) with strict Red-Green-Refactor methodology: -Follow [TDD guidelines](.pair/knowledge/guidelines/testing/test-strategy/tdd-test-driven-development.md) with strict methodology: +1. **RED Phase** — Write or modify ONLY test code. Tests MUST fail. No implementation code changes. Session ends when tests are written and failing. -- **Red-Green-Refactor Cycle**: All development code must follow strict TDD methodology -- **Test First**: ALWAYS write tests before implementation code -- **Failing Tests Required**: Tests must fail initially to validate correct behavior testing -- **Single Session Rule**: NEVER modify both tests and implementation code in the same session -- **Complete Cycle**: Each development task requires complete Red-Green-Refactor cycle execution +2. **GREEN Phase** — Write or modify ONLY implementation code. Write minimal code to make tests pass. No test code changes. Session ends when all tests pass. -### TDD Session Management +3. **REFACTOR Phase** — Improve code structure without changing behavior. Both test and production code may be cleaned up. All tests must remain green. Session ends when refactoring objectives are complete. -**Session Types and Restrictions (Development Tasks Only):** - -1. **Test Writing Session (RED Phase)**: - - - Write or modify ONLY test code following [unit testing guidelines](.pair/knowledge/guidelines/testing/unit-testing/README.md) - - NO implementation code changes allowed - - Tests MUST fail when first written - - Session ends when tests are written and failing - -2. **Implementation Session (GREEN Phase)**: - - - Write or modify ONLY implementation code following [code design principles](.pair/knowledge/guidelines/code-design/design-principles/README.md) - - NO test code changes allowed - - Write minimal code to achieve green state - - Session ends when all tests pass - -3. **Refactoring Session (REFACTOR Phase)**: - - Improve code structure without changing behavior - - Both tests and code may be refactored for clarity - - All tests must remain green throughout - - Session ends when refactoring objectives complete +**CRITICAL**: NEVER modify both tests and implementation code in the same session. ### Direct Implementation (Non-Development Tasks) -**For Documentation, Configuration, and Research tasks:** - -- **No TDD Required**: These tasks don't require test-driven development -- **Direct Implementation**: Implement task requirements directly -- **Quality Focus**: Follow documentation standards, configuration best practices, or research methodology -- **Validation**: Verify against task acceptance criteria without formal testing +- Implement task requirements directly — no TDD required +- Follow documentation standards, configuration best practices, or research methodology +- Validate against task acceptance criteria ## Implementation Flow ### Phase 0: Story & Task Analysis (BLOCKING PREREQUISITE) -**🚫 CRITICAL: NO IMPLEMENTATION WITHOUT COMPLETE STORY & TASK UNDERSTANDING** +**HALT ALL WORK** if this phase is not successfully completed. -``` -1. Read Complete User Story → Load from PM tool, understand business value -2. Analyze All Story Tasks → Validate task breakdown completeness -3. Validate Story State → Must be "In Progress" and assigned to me -4. Confirm Task Specifications → Ensure all implementation details present -``` - -**Story Reading Requirements:** - -- **Load story from configured PM tool** per [way-of-working.md](.pair/adoption/tech/way-of-working.md) -- **Understand business value and acceptance criteria** completely -- **Verify story status**: Must be "In Progress" and assigned to developer -- **Confirm epic context**: Understand how story fits in larger initiative - -**Task Analysis Requirements:** - -- **Read ALL tasks in the story** - never implement partial understanding -- **Validate each task follows [task template](.pair/knowledge/guidelines/collaboration/templates/task-template.md)**: - - Complete task information (ID, parent story, assignee, priority, status) - - Detailed implementation approach (technical design, files, dependencies) - - Acceptance criteria (deliverable, quality standards, verification) - - Development workflow (TDD approach, implementation steps, testing) +1. **Read complete user story** from PM tool — understand business value and acceptance criteria +2. **Analyze ALL tasks** in the story — validate each follows the task template +3. **Validate story state** — must be "In Progress" and assigned to developer +4. **Confirm task specifications** — all implementation details present -**BLOCKING VALIDATION:** -If ANY of these conditions are not met, **HALT ALL WORK**: - -- [ ] Story not fully loaded and understood -- [ ] Tasks incomplete or missing implementation details -- [ ] Story not in "In Progress" state -- [ ] Story not assigned to implementing developer -- [ ] Task specifications don't follow template requirements -- [ ] Unclear libraries to use or implementation approach - -**Developer Confirmation Required:** -_"I've analyzed Story [STORY-ID]: [TITLE] with [X] tasks. All task specifications are complete and follow the template. Story is in 'In Progress' state and assigned to me. I understand the business value and technical requirements. Ready to proceed with implementation?"_ +Present analysis to developer and get explicit confirmation before proceeding. ### Phase 1: Setup & Context Loading -``` -1. Validate Prerequisites → Check blockers and story state -2. Load Technical Context → Architecture, tech stack, existing patterns -3. Create Feature Branch → Standard naming with story reference -4. Choose Commit Strategy → Per-task or per-story completion -``` - -**Branch Requirements:** -Follow [branch template](.pair/knowledge/guidelines/collaboration/templates/branch-template.md) with pattern: - -``` -/#- -``` - -**Examples:** - -- `feature/#US-123-user-authentication` -- `bug/#BUG-456-login-validation-error` -- `docs/#DOC-789-api-documentation` - -**Branch Creation:** - -```bash -# Ensure clean main branch -git checkout main -git pull origin main - -# Create feature branch with story reference -git checkout -b feature/#US-123-user-authentication - -# Set upstream tracking -git push -u origin feature/#US-123-user-authentication -``` - -**Association**: Link branch to story in PM tool +1. **Load technical context** — architecture, tech stack, way-of-working from adoption files +2. **Create or switch to feature branch** — per [branch template](../guidelines/collaboration/templates/branch-template.md): `/#-` +3. **Choose commit strategy** (for multi-task stories) — per-task commits (recommended, granular) or per-story commit (single commit at end). Single PR per story regardless. ### Phase 2: Task-by-Task Implementation -``` -For each task in story: - 1. Update Session State → Set active task and implementation mode - 2. Validate Task Completeness → Ensure all required info present - 3. Execute Implementation → TDD cycle OR Direct implementation - 4. Update Task Status → Mark complete in PM tool - 5. Commit Changes → Based on chosen strategy - 6. Progress to Next → Update state for next task -``` - -**Task Validation Requirements:** -Based on [task template](.pair/knowledge/guidelines/collaboration/templates/task-template.md), each task must have: +Process tasks **sequentially**. For each task: -- Complete task information (ID, parent story, assignee, priority, status) -- Detailed implementation approach (technical design, files to modify/create, dependencies) -- Acceptance criteria (primary deliverable, quality standards, verification methods) -- Development workflow (TDD approach, implementation steps, testing strategy) +1. **Set active task** — update session state +2. **Validate task completeness** — HALT if task spec is incomplete +3. **Execute implementation** — TDD cycle (RED → GREEN → REFACTOR) for development tasks, direct implementation for non-development tasks +4. **Verify quality** — run quality gates per [quality standards](../guidelines/quality-assurance/quality-standards/README.md). HALT on failure. +5. **Commit** (if per-task strategy) — per [commit template](../guidelines/collaboration/templates/commit-template.md) +6. **Mark task complete** — update story checklist, progress to next task -**Implementation Rules by Task Type:** - -**Development Tasks (TDD Mode):** - -- **RED**: Write failing tests only, apply [unit testing guidelines](.pair/knowledge/guidelines/testing/unit-testing/README.md) -- **GREEN**: Write minimal implementation only, follow [code design principles](.pair/knowledge/guidelines/code-design/design-principles/README.md) -- **REFACTOR**: Improve structure only, keep tests green - -**Non-Development Tasks (Direct Mode):** - -- **Documentation**: Follow [documentation standards](.pair/knowledge/guidelines/user-experience/markdown-templates.md) -- **Configuration**: Apply [infrastructure guidelines](.pair/knowledge/guidelines/infrastructure/README.md) -- **Research**: Document findings and recommendations - -**Task Status Updates:** - -- Mark completed task as ✅ in story checklist -- Update progress counter (e.g., "Tasks: 3/5 completed") -- Preserve all story content (acceptance criteria, etc.) - -### Phase 3: Commit & Push Workflow - -**Strategy Selection (Choose Once Per Story):** - -**Option A: Per-Task Commits** - -``` -After each task completion: -1. Stage changes → git add . -2. Commit with task reference → Follow commit standards -3. Push to remote → Enable backup and collaboration -``` +### Phase 3: Commit, Push & PR -**Option B: Per-Story Commits** - -``` -After all tasks complete: -1. Stage all changes → git add . -2. Commit with story summary → Reference all completed tasks -3. Push final implementation → Ready for PR creation -``` - -**Commit Message Format:** -Follow [commit template](.pair/knowledge/guidelines/collaboration/templates/commit-template.md): - -**For Development Tasks (TDD):** - -``` -[US-XXX] [type]: [task-description] - -- Implement [specific functionality] -- TDD: [RED|GREEN|REFACTOR] phase -- Task: [TASK-ID] - [task title] - -Refs: #story-id -``` - -**For Non-Development Tasks:** - -``` -[US-XXX] docs: [task-description] -# or -[US-XXX] config: [task-description] -# or -[US-XXX] chore: [task-description] - -- [Description of changes] -- Task: [TASK-ID] - [task title] - -Refs: #story-id -``` - -### Phase 4: Quality Validation & Handoff - -``` -1. Run Quality Checks → Tests, lints, security scans -2. Validate Implementation → All acceptance criteria met -3. Update Story Status → Ready for review -4. Prepare for PR Creation → Branch ready for pull request -``` - -**Quality Gates:** -Apply [quality standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md): - -**For Development Tasks:** - -- [ ] All tests passing (TDD cycles complete) -- [ ] All tasks marked complete in story -- [ ] All acceptance criteria addressed -- [ ] Code follows [code design guidelines](.pair/knowledge/guidelines/code-design/README.md) -- [ ] Only approved libraries from [tech-stack.md](.pair/adoption/tech/tech-stack.md) used -- [ ] Version consistency maintained per [architecture decisions](.pair/adoption/tech/architecture.md) - -**For Non-Development Tasks:** - -- [ ] All tasks marked complete in story -- [ ] All acceptance criteria addressed -- [ ] Documentation follows [markdown standards](.pair/knowledge/guidelines/user-experience/markdown-templates.md) -- [ ] Configuration follows [infrastructure guidelines](.pair/knowledge/guidelines/infrastructure/README.md) -- [ ] Research findings properly documented and recommendations clear - -### Phase 5: Pull Request Creation & Review Setup - -``` -1. Generate PR Description → Using PR template with complete context -2. Assign Reviewers → Based on code expertise and team patterns -3. Create Pull Request → With proper title, description, and metadata -4. Update Project Status → Mark story as "In Review" -5. Setup Review Communication → Notify reviewers and establish channels -``` - -**PR Creation Requirements:** -Follow [PR template](.pair/knowledge/guidelines/collaboration/templates/pr-template.md) structure: - -**PR Title Format:** - -``` -[US-XXX] [type]: [brief description of changes] -``` - -**PR Description Structure:** - -- **Summary**: What changed and why -- **Story Context**: User story reference and acceptance criteria coverage -- **Changes Made**: Implementation details and files affected -- **Testing**: Test coverage and validation steps -- **Quality Assurance**: Code quality checklist and review areas -- **Deployment Information**: Environment impact and deployment notes - -**Reviewer Assignment Strategy:** - -- **Code Area Experts**: Assign reviewers with expertise in affected components -- **Team Rotation**: Follow team patterns for knowledge distribution -- **Required Reviewers**: Include mandatory reviewers per team policy -- **Knowledge Sharing**: Balance expertise with learning opportunities - -**Project Status Update:** - -- Update story status from "Implementation Complete" to "In Review" -- Add PR reference to all related tasks in PM tool -- Update epic progress to reflect code review phase -- Maintain traceability: Story → Tasks → Commits → PR - -## Key References - -**Technical Constraints:** - -- **Libraries**: Only approved from [tech-stack.md](.pair/adoption/tech/tech-stack.md) or task-specified -- **Architecture**: Follow [architecture decisions](.pair/adoption/tech/architecture.md) and [guidelines](.pair/knowledge/guidelines/architecture/README.md) -- **Quality**: Apply [code design](.pair/knowledge/guidelines/code-design/README.md), [security](.pair/knowledge/guidelines/quality-assurance/security/README.md), and [quality standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) - -**Emergency Procedures:** - -- **Story Issues**: Use [08-refine-story](08-how-to-refine-a-user-story.md) or [09-create-tasks](09-how-to-create-tasks.md) -- **Technical Blockers**: Halt implementation, request task updates, consult relevant guidelines -- **Process Issues**: Reset to last stable state, escalate to developer +1. **Final commit** (if per-story strategy) — per [commit template](../guidelines/collaboration/templates/commit-template.md) +2. **Push branch** to remote +3. **Create PR** — per [PR template](../guidelines/collaboration/templates/pr-template.md), linking the user story issue +4. **Update story status** to "In Review" in PM tool ## Success Criteria **Story Implementation Complete When:** -- [ ] Phase 0: Story & Task Analysis completed successfully -- [ ] All tasks marked ✅ in story checklist +- [ ] Phase 0 completed successfully +- [ ] All tasks marked complete in story checklist - [ ] All acceptance criteria validated - [ ] Implementation matches task specifications exactly +- [ ] Quality gates passed per [quality standards](../guidelines/quality-assurance/quality-standards/README.md) - [ ] Code committed and pushed to feature branch -- [ ] Quality gates passed per [quality standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) -- [ ] Pull request created with comprehensive description using [PR template](.pair/knowledge/guidelines/collaboration/templates/pr-template.md) -- [ ] Reviewers assigned based on expertise and team patterns -- [ ] Story status updated to "In Review" in PM tool -- [ ] Ready for code review process +- [ ] PR created with comprehensive description +- [ ] Story status updated to "In Review" **Additional for Development Tasks:** -- [ ] All TDD cycles completed (RED-GREEN-REFACTOR) +- [ ] All TDD cycles completed (RED → GREEN → REFACTOR) - [ ] All tests passing with adequate coverage -**Additional for Non-Development Tasks:** +## Emergency Procedures -- [ ] Documentation meets [markdown standards](.pair/knowledge/guidelines/user-experience/markdown-templates.md) -- [ ] Configuration follows [infrastructure guidelines](.pair/knowledge/guidelines/infrastructure/README.md) -- [ ] Research findings properly documented +- **Story/Task Issues**: Use [08-refine-story](08-how-to-refine-a-user-story.md) or [09-create-tasks](09-how-to-create-tasks.md) +- **Technical Blockers**: HALT, request task updates, consult relevant guidelines +- **Process Issues**: Reset to last stable state, escalate to developer ## References -### Templates & Guidelines - -- [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) - Complete task specification format -- [Branch Template](.pair/knowledge/guidelines/collaboration/templates/branch-template.md) - Branch naming standards -- [Commit Template](.pair/knowledge/guidelines/collaboration/templates/commit-template.md) - Commit message format -- [PR Template](.pair/knowledge/guidelines/collaboration/templates/pr-template.md) - Pull request structure - -### Technical Standards +### Templates -- [Tech Stack](.pair/adoption/tech/tech-stack.md) - Approved libraries and versions -- [Architecture Decisions](.pair/adoption/tech/architecture.md) - System architecture patterns -- [Way of Working](.pair/adoption/tech/way-of-working.md) - Development process configuration +- [Task Template](../guidelines/collaboration/templates/task-template.md) — task specification format +- [Branch Template](../guidelines/collaboration/templates/branch-template.md) — branch naming standards +- [Commit Template](../guidelines/collaboration/templates/commit-template.md) — commit message format +- [PR Template](../guidelines/collaboration/templates/pr-template.md) — pull request structure -### Development Guidelines +### Adoption & Standards -- [TDD Guidelines](.pair/knowledge/guidelines/testing/test-strategy/tdd-test-driven-development.md) - Test-driven development methodology -- [Unit Testing](.pair/knowledge/guidelines/testing/unit-testing/README.md) - Testing standards and practices -- [Code Design](.pair/knowledge/guidelines/code-design/README.md) - Code design principles and patterns -- [Quality Standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) - Quality gates and criteria +- [Tech Stack](../../adoption/tech/tech-stack.md) — approved libraries and versions +- [Architecture](../../adoption/tech/architecture.md) — system architecture patterns +- [Way of Working](../../adoption/tech/way-of-working.md) — development process -### Process Guidelines +### Guidelines -- [Project Management Framework](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - PM tool usage -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) - Security requirements -- [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) - Configuration standards -- [Documentation Standards](.pair/knowledge/guidelines/user-experience/markdown-templates.md) - Markdown formatting +- [TDD Guidelines](../guidelines/testing/test-strategy/tdd-test-driven-development.md) — test-driven development methodology +- [Unit Testing](../guidelines/testing/unit-testing/README.md) — testing standards +- [Code Design](../guidelines/code-design/README.md) — code design principles +- [Quality Standards](../guidelines/quality-assurance/quality-standards/README.md) — quality gates ### Related Workflows -- [08-how-to-refine-a-user-story.md](08-how-to-refine-a-user-story.md) - Story refinement process -- [09-how-to-create-tasks.md](09-how-to-create-tasks.md) - Task creation workflow -- [11-how-to-code-review.md](11-how-to-code-review.md) - Code review process +- [08-how-to-refine-a-user-story.md](08-how-to-refine-a-user-story.md) — story refinement +- [09-how-to-create-tasks.md](09-how-to-create-tasks.md) — task creation +- [11-how-to-code-review.md](11-how-to-code-review.md) — code review ## Next Steps diff --git a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/11-how-to-code-review.md b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/11-how-to-code-review.md index 51bd98ce..756d39c8 100644 --- a/packages/knowledge-hub/dataset/.pair/knowledge/how-to/11-how-to-code-review.md +++ b/packages/knowledge-hub/dataset/.pair/knowledge/how-to/11-how-to-code-review.md @@ -31,37 +31,37 @@ CODE REVIEW STATE: - **Review ONLY completed PRs** - validate existing pull request with implemented changes - **CRITICAL ADR validation** - verify all new technical decisions are properly documented -- **Follow code review template** per [code-review-template.md](.pair/knowledge/guidelines/collaboration/templates/code-review-template.md) +- **Follow code review template** per [code-review-template.md](../guidelines/collaboration/templates/code-review-template.md) - **Validate story requirements** from the user story being implemented -- **Apply technical standards** from [adoption guidelines](.pair/adoption/tech) and [quality standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) +- **Apply technical standards** from [adoption guidelines](../../adoption/tech) and [quality standards](../guidelines/quality-assurance/quality-standards/README.md) **CRITICAL**: If new libraries/patterns found without ADR documentation: - **HALT merge process immediately** -- **Request ADR creation** following [ADR template](.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md) +- **Request ADR creation** following [ADR template](../guidelines/architecture/decision-frameworks/adr-process.md) - **Update adoption documents** to include new decisions - **Do NOT proceed** until technical decisions are properly documented ### Technical Alignment Requirements -- **Architecture**: Follow patterns from [architecture decisions](.pair/adoption/tech/architecture.md) -- **Technology Stack**: Use ONLY libraries from [tech-stack.md](.pair/adoption/tech/tech-stack.md) -- **Code Quality**: Apply [code design guidelines](.pair/knowledge/guidelines/code-design/README.md) -- **Testing**: Follow [testing strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) -- **Security**: Validate [security guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) +- **Architecture**: Follow patterns from [architecture decisions](../../adoption/tech/architecture.md) +- **Technology Stack**: Use ONLY libraries from [tech-stack.md](../../adoption/tech/tech-stack.md) +- **Code Quality**: Apply [code design guidelines](../guidelines/code-design/README.md) +- **Testing**: Follow [testing strategy](../guidelines/testing/test-strategy/README.md) +- **Security**: Validate [security guidelines](../guidelines/quality-assurance/security/README.md) ## Prerequisites & Guardrails ### 🚫 Critical Blockers - **Active PR Required**: Pull request must exist and be ready for review -- **PM Tool Configured**: Must exist in [way-of-working.md](.pair/adoption/tech/way-of-working.md) +- **PM Tool Configured**: Must exist in [way-of-working.md](../../adoption/tech/way-of-working.md) - **Story Context Available**: User story must be accessible and understood - **PR Analysis Complete**: Phase 0 must be completed before any other work ### 📋 Access Requirements -Follow [project management tool guidelines](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) for tool-specific access procedures based on the configured tool in [way-of-working.md](.pair/adoption/tech/way-of-working.md). +Follow [project management tool guidelines](../guidelines/collaboration/project-management-tool/README.md) for tool-specific access procedures based on the configured tool in [way-of-working.md](../../adoption/tech/way-of-working.md). **Access Rules:** @@ -128,7 +128,7 @@ Scan implementation for introduction of: **PR Loading Requirements:** -- **Load PR from configured PM tool** per [way-of-working.md](.pair/adoption/tech/way-of-working.md) +- **Load PR from configured PM tool** per [way-of-working.md](../../adoption/tech/way-of-working.md) - **Understand implementation scope** and files changed - **Verify PR status**: Must be open and ready for review - **Extract story reference**: Link between PR and user story @@ -173,11 +173,11 @@ Scan implementation for: **For Each New Technical Decision Found:** -- [ ] **ADR Exists** - Verify ADR document in [architecture.md](.pair/adoption/tech/architecture.md) +- [ ] **ADR Exists** - Verify ADR document in [architecture.md](../../adoption/tech/architecture.md) - [ ] **ADR Quality** - Contains context, options, and rationale -- [ ] **Adoption Updated** - [tech-stack.md](.pair/adoption/tech/tech-stack.md) includes new dependencies +- [ ] **Adoption Updated** - [tech-stack.md](../../adoption/tech/tech-stack.md) includes new dependencies - [ ] **Version Consistency** - Same versions across all workspaces -- [ ] **Guidelines Updated** - [Technical guidelines](.pair/knowledge/guidelines) reflect new approaches +- [ ] **Guidelines Updated** - [Technical guidelines](../guidelines) reflect new approaches **🚫 BLOCKING ISSUES - IMMEDIATE REVIEW FAILURE:** ❌ **Undocumented New Library** - New dependency without ADR or adoption update @@ -187,16 +187,16 @@ Scan implementation for: **Actions for Missing Documentation:** 1. **HALT merge process** - Set PR status to "changes-requested" -2. **Create ADR task** - Following [ADR template](.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md) +2. **Create ADR task** - Following [ADR template](../guidelines/architecture/decision-frameworks/adr-process.md) 3. **Update adoption documents** - Include new decisions in adoption files 4. **Re-review required** - After documentation completed **Technical Standards Validation:** -- **Code Quality** - Apply [code design guidelines](.pair/knowledge/guidelines/code-design/README.md) -- **Architecture** - Follow [architecture decisions](.pair/adoption/tech/architecture.md) -- **Security** - Validate [security guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) -- **Testing** - Verify [testing strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) +- **Code Quality** - Apply [code design guidelines](../guidelines/code-design/README.md) +- **Architecture** - Follow [architecture decisions](../../adoption/tech/architecture.md) +- **Security** - Validate [security guidelines](../guidelines/quality-assurance/security/README.md) +- **Testing** - Verify [testing strategy](../guidelines/testing/test-strategy/README.md) ### Phase 2: Story & Requirements Validation @@ -216,7 +216,7 @@ Scan implementation for: **Quality Assurance:** -- **Testing Coverage** - Adequate test coverage per [testing strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) +- **Testing Coverage** - Adequate test coverage per [testing strategy](../guidelines/testing/test-strategy/README.md) - **Documentation** - Required documentation completed - **Performance** - No performance regressions - **Security** - Security requirements satisfied @@ -233,7 +233,7 @@ Scan implementation for: **Review Report Generation (MANDATORY):** -- **Use template**: Follow [code-review-template.md](.pair/knowledge/guidelines/collaboration/templates/code-review-template.md) structure exactly +- **Use template**: Follow [code-review-template.md](../guidelines/collaboration/templates/code-review-template.md) structure exactly - **Generate comprehensive report**: Include all sections - summary, technical analysis, security, performance - **Post as PR comment**: Add complete review report directly to GitHub PR comments - **Include all findings**: Document critical, major, minor issues with specific solutions and code examples @@ -274,7 +274,7 @@ Scan implementation for: **Squash and Merge Process:** - **Use GitHub squash merge** → Maintains clean history -- **Apply commit template format** per [commit template](.pair/knowledge/guidelines/collaboration/templates/commit-template.md): +- **Apply commit template format** per [commit template](../guidelines/collaboration/templates/commit-template.md): ``` [US-XXX] feat: story summary @@ -301,7 +301,7 @@ Closes #T-XXX, #T-YYY - [ ] PR context loaded with story/task validation - [ ] ADR and adoption documentation validated for all new technical decisions - [ ] All technical standards verified against adoption guidelines -- [ ] **Review report generated** using [code-review-template.md](.pair/knowledge/guidelines/collaboration/templates/code-review-template.md) +- [ ] **Review report generated** using [code-review-template.md](../guidelines/collaboration/templates/code-review-template.md) - [ ] **Report posted as PR comment** in GitHub with comprehensive findings - [ ] PR status updated appropriately (pending/changes-requested/approved) - [ ] Review decision made (approved/changes-requested/tech-debt) @@ -317,31 +317,31 @@ Closes #T-XXX, #T-YYY ### Templates & Guidelines -- [Code Review Template](.pair/knowledge/guidelines/collaboration/templates/code-review-template.md) - Comprehensive review structure and format -- [ADR Template](.pair/knowledge/guidelines/architecture/decision-frameworks/adr-process.md) - Architecture Decision Record format for technical decisions -- [Task Template](.pair/knowledge/guidelines/collaboration/templates/task-template.md) - Task creation format for follow-up work -- [Branch Template](.pair/knowledge/guidelines/collaboration/templates/branch-template.md) - Branch naming standards validation -- [Commit Template](.pair/knowledge/guidelines/collaboration/templates/commit-template.md) - Squash commit format for merge +- [Code Review Template](../guidelines/collaboration/templates/code-review-template.md) - Comprehensive review structure and format +- [ADR Template](../guidelines/architecture/decision-frameworks/adr-process.md) - Architecture Decision Record format for technical decisions +- [Task Template](../guidelines/collaboration/templates/task-template.md) - Task creation format for follow-up work +- [Branch Template](../guidelines/collaboration/templates/branch-template.md) - Branch naming standards validation +- [Commit Template](../guidelines/collaboration/templates/commit-template.md) - Squash commit format for merge ### Technical Standards -- [Tech Stack](.pair/adoption/tech/tech-stack.md) - Approved libraries and versions validation -- [Architecture Decisions](.pair/adoption/tech/architecture.md) - System architecture patterns compliance -- [Way of Working](.pair/adoption/tech/way-of-working.md) - Development process and PM tool configuration +- [Tech Stack](../../adoption/tech/tech-stack.md) - Approved libraries and versions validation +- [Architecture Decisions](../../adoption/tech/architecture.md) - System architecture patterns compliance +- [Way of Working](../../adoption/tech/way-of-working.md) - Development process and PM tool configuration ### Quality Standards -- [Quality Standards](.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) - Quality gates and validation criteria -- [Code Design Guidelines](.pair/knowledge/guidelines/code-design/README.md) - Code quality and design principles -- [Testing Strategy](.pair/knowledge/guidelines/testing/test-strategy/README.md) - Testing coverage and quality requirements -- [Security Guidelines](.pair/knowledge/guidelines/quality-assurance/security/README.md) - Security validation requirements +- [Quality Standards](../guidelines/quality-assurance/quality-standards/README.md) - Quality gates and validation criteria +- [Code Design Guidelines](../guidelines/code-design/README.md) - Code quality and design principles +- [Testing Strategy](../guidelines/testing/test-strategy/README.md) - Testing coverage and quality requirements +- [Security Guidelines](../guidelines/quality-assurance/security/README.md) - Security validation requirements ### Process Guidelines -- [Project Management Framework](.pair/knowledge/guidelines/collaboration/project-management-tool/README.md) - PM tool usage and integration -- [Architecture Guidelines](.pair/knowledge/guidelines/architecture/README.md) - Architectural patterns and compliance -- [Infrastructure Guidelines](.pair/knowledge/guidelines/infrastructure/README.md) - Infrastructure and deployment standards -- [Performance Guidelines](.pair/knowledge/guidelines/quality-assurance/performance/README.md) - Performance standards and optimization +- [Project Management Framework](../guidelines/collaboration/project-management-tool/README.md) - PM tool usage and integration +- [Architecture Guidelines](../guidelines/architecture/README.md) - Architectural patterns and compliance +- [Infrastructure Guidelines](../guidelines/infrastructure/README.md) - Infrastructure and deployment standards +- [Performance Guidelines](../guidelines/quality-assurance/performance/README.md) - Performance standards and optimization ### Related Workflows diff --git a/packages/knowledge-hub/dataset/.skills/capability/record-decision/SKILL.md b/packages/knowledge-hub/dataset/.skills/capability/record-decision/SKILL.md new file mode 100644 index 00000000..a228ddb6 --- /dev/null +++ b/packages/knowledge-hub/dataset/.skills/capability/record-decision/SKILL.md @@ -0,0 +1,130 @@ +--- +name: record-decision +description: >- + Records an architectural or non-architectural decision. Architectural + decisions produce an ADR; non-architectural decisions produce an ADL entry. + Both always update the relevant adoption files. Invocable independently or + composed by /implement and /review. +--- + +# /record-decision — Decision Recorder + +Record a technical decision as either an ADR (architectural) or ADL (non-architectural). Always update the corresponding adoption files to keep them as the single source of truth for "what we use now." + +## Arguments + +| Argument | Required | Description | +|----------|----------|-------------| +| `$type` | Yes | Decision type: `architectural` or `non-architectural` | +| `$topic` | Yes | Short kebab-case topic name (e.g., `streaming-downloads`, `date-library-choice`) | +| `$summary` | No | One-line summary of the decision (will be asked interactively if omitted) | + +## Core Rule: ADR and ADL Are Mutually Exclusive + +- **Architectural decision** → ADR file + adoption update. Never ADL. +- **Non-architectural decision** → ADL file + adoption update. Never ADR. +- **Adoption update is always required** regardless of decision type. +- Adoption files = "what we use now." ADR/ADL = "why we decided." + +## Algorithm + +### Step 1: Classify Decision Type + +1. **Check**: Is `$type` provided? If yes, use it. +2. **Act**: If not provided, ask the developer: + > Is this decision **architectural** (affects system structure, patterns, service boundaries, quality attributes) or **non-architectural** (library choice, convention adoption, tooling preference)? +3. **Verify**: Decision type is set to `architectural` or `non-architectural`. + +### Step 2: Detect Existing Decision + +1. **Check**: Search for existing decision files matching `$topic`: + - If `architectural`: scan `adoption/tech/adr/` for files containing `$topic` in filename. + - If `non-architectural`: scan `adoption/decision-log/` for files containing `$topic` in filename. +2. **Skip**: If no existing file found, proceed to Step 3 (create new). +3. **Act**: If existing file found, ask the developer: + > Found existing decision: `[filename]`. Do you want to **update** this decision or **create a new one**? + - **Update**: Read existing file, present current content, proceed to Step 4 with update mode. + - **Create new**: Proceed to Step 3 with create mode (for cases where the topic evolved into a distinct decision). +4. **Verify**: Mode is set to `create` or `update`. + +### Step 3: Write Decision File + +**File naming**: `YYYY-MM-DD-.md` (today's date, one file per decision). + +**If `architectural` → ADR:** + +1. **Check**: Does `adoption/tech/adr/` directory exist? +2. **Act**: If not, create it. +3. **Act**: Create (or update) the ADR file at `adoption/tech/adr/YYYY-MM-DD-.md` following the standalone [ADR template](../../../.pair/knowledge/guidelines/collaboration/templates/adr-template.md). Fill in all sections: Status, Date, Context, Options Considered, Decision, Consequences, and Adoption Impact. +4. **Verify**: ADR file exists with complete content following the template structure. + +**If `non-architectural` → ADL:** + +1. **Check**: Does `adoption/decision-log/` directory exist? +2. **Act**: If not, create it. +3. **Act**: Create (or update) the ADL file at `adoption/decision-log/YYYY-MM-DD-.md` following the standalone [ADL template](../../../.pair/knowledge/guidelines/collaboration/templates/adl-template.md). Fill in all sections: Date, Status, Category, Context, Decision, Alternatives Considered, Consequences, and Adoption Impact. +4. **Verify**: ADL file exists with complete content following the template structure. + +### Step 4: Update Adoption Files + +This step is **always required** — adoption is the single source of truth. + +1. **Check**: Identify which adoption files are affected by this decision: + - [tech-stack.md](../../../.pair/adoption/tech/tech-stack.md) — if the decision involves libraries, frameworks, or tools + - [architecture.md](../../../.pair/adoption/tech/architecture.md) — if the decision involves architectural patterns, boundaries, or infrastructure + - [way-of-working.md](../../../.pair/adoption/tech/way-of-working.md) — if the decision involves process, workflow, or tooling conventions + - Other adoption files as relevant +2. **Act**: For each affected adoption file: + - Read current content. + - Add or update the relevant entry to reflect the decision. + - Preserve existing content — only add/modify the affected section. +3. **Verify**: Each updated adoption file reflects the current state of facts. + +### Step 5: Consistency Check + +1. **Check**: Re-read the decision file (ADR or ADL) and all updated adoption files. +2. **Act**: Verify that every claim in the decision file is reflected in adoption, and vice versa. +3. **Verify**: If inconsistency found, report to developer and propose correction. + +## Output Format + +``` +DECISION RECORDED: +├── Type: [Architectural (ADR) | Non-architectural (ADL)] +├── File: [path to decision file] +├── Mode: [Created | Updated] +├── Adoption: [list of updated adoption files] +└── Status: [Consistent | Inconsistency detected — details] +``` + +## Composition Interface + +When composed by `/implement` or `/review`: + +- **Input**: The composing skill detects a decision need and invokes `/record-decision` with `$type` and `$topic`. +- **Output**: Returns the path to the decision file and list of updated adoption files. +- The composing skill includes the decision file in the next commit. + +When invoked **independently**: + +- Interactive: asks for type, topic, and summary if not provided as arguments. +- Writes files and reports results. Developer commits the changes. + +## Edge Cases + +- **Same topic + same date**: If a file `YYYY-MM-DD-.md` already exists and the developer chose "create new," append an incremented suffix: `YYYY-MM-DD--2.md`. +- **Adoption file doesn't exist**: Create it with the decision content as the initial entry. Warn the developer that a new adoption file was created. +- **Decision supersedes another**: Set the old decision's status to "Superseded by [new file]" and the new decision references the old one. + +## Graceful Degradation + +- If [ADR template](../../../.pair/knowledge/guidelines/collaboration/templates/adr-template.md) is not found, use the minimal ADR structure: Status, Date, Context, Decision, Consequences, Adoption Impact. +- If [ADL template](../../../.pair/knowledge/guidelines/collaboration/templates/adl-template.md) is not found, use the minimal ADL structure: Date, Status, Context, Decision, Consequences, Adoption Impact. +- If adoption directories don't exist, create them and warn: "Created adoption directory — this appears to be a new project." + +## Notes + +- ADR and ADL are mutually exclusive. Never write both for the same decision. +- Adoption files are always updated. A decision without adoption update is incomplete. +- Date-based naming (`YYYY-MM-DD-.md`) ensures sortability and avoids numbering conflicts. +- This skill modifies files: decision files and adoption files. All changes should be committed together. diff --git a/packages/knowledge-hub/dataset/.skills/capability/verify-quality/SKILL.md b/packages/knowledge-hub/dataset/.skills/capability/verify-quality/SKILL.md new file mode 100644 index 00000000..818c5bb3 --- /dev/null +++ b/packages/knowledge-hub/dataset/.skills/capability/verify-quality/SKILL.md @@ -0,0 +1,104 @@ +--- +name: verify-quality +description: >- + Checks quality gates against the current codebase. Reads project-specific + quality gate command from way-of-working adoption and universal standards + from quality-standards guidelines. Gates already passing are skipped. + Invocable independently or composed by /implement and /review. +--- + +# /verify-quality — Quality Gate Checker + +Validate the current codebase against quality gates. Two sources of truth: + +- **[way-of-working.md](../../../.pair/adoption/tech/way-of-working.md)** — project-specific quality gate command and process (e.g., `pnpm quality-gate`). This is "what command we run." +- **[quality-standards](../../../.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md)** — universal quality standards (gates, DoD, checklists). This is "what we check." + +Only check gates that are not already passing. + +## Arguments + +| Argument | Required | Description | +|----------|----------|-------------| +| `$scope` | No | Limit checking to specific gates: `code-quality`, `tests`, `lint`, `all` (default: `all`) | + +## Algorithm + +Execute each gate in order. For every gate, follow the **check → skip → act → verify** pattern. + +### Step 1: Read Adoption Quality Gate Configuration + +1. **Check**: Read [way-of-working.md](../../../.pair/adoption/tech/way-of-working.md) and look for a **Quality Gates** section declaring the project-specific quality gate command (e.g., `pnpm quality-gate`). +2. **Skip**: If `way-of-working.md` has no Quality Gates section, fall back to `package.json` scripts for detectable gate commands (e.g., `test`, `lint`, `ts:check`). +3. **Act**: If found, record the command for use in Step 5. Also note any sub-checks listed (e.g., type checking, testing, linting, formatting). + +### Step 2: Lint Gate + +1. **Check**: Run the project linter (e.g., `pnpm lint` or `turbo lint`). Capture output. +2. **Skip**: If zero violations, report "Lint: PASS" and move to Step 3. +3. **Act**: If violations found, report each violation with file and line. +4. **Verify**: After developer fixes, re-run linter to confirm zero violations. + +### Step 3: Type Check Gate + +1. **Check**: Run the type checker (e.g., `pnpm tsc --noEmit` or `turbo build`). Capture output. +2. **Skip**: If zero errors, report "Type Check: PASS" and move to Step 4. +3. **Act**: If errors found, report each error with file and line. +4. **Verify**: After developer fixes, re-run type checker to confirm zero errors. + +### Step 4: Test Gate + +1. **Check**: Run the test suite (e.g., `pnpm test` or `turbo test`). Capture output including coverage. +2. **Skip**: If all tests pass, report "Tests: PASS (N tests, X% coverage)" and move to Step 5. +3. **Act**: If tests fail, report each failure with test name, file, and assertion message. +4. **Verify**: After developer fixes, re-run tests to confirm all pass. + +### Step 5: Aggregate Quality Gate + +If a project-level quality gate command exists (from Step 1): + +1. **Check**: Run the aggregate command (e.g., `pnpm quality-gate`). +2. **Skip**: If exit code 0, report "Quality Gate: PASS" and move to output. +3. **Act**: If non-zero exit, report the failing sub-gates. +4. **Verify**: After developer fixes, re-run to confirm pass. + +## Output Format + +Present results as: + +``` +QUALITY GATE REPORT: +├── Lint: [PASS | FAIL — N violations] +├── Type Check: [PASS | FAIL — N errors] +├── Tests: [PASS — N tests, X% coverage | FAIL — N failures] +└── Aggregate: [PASS | FAIL | N/A] + +RESULT: [ALL GATES PASS | BLOCKED — N gates failing] +``` + +## Composition Interface + +When composed by `/implement` or `/review`: + +- **Input**: The composing skill invokes `/verify-quality` after implementation or before commit. +- **Output**: Returns PASS or FAIL with details. The composing skill decides what to do: + - `/implement`: HALT on FAIL — developer must fix before commit. + - `/review`: Report FAIL as review finding — does not block review completion. + +When invoked **independently**: + +- Run all gates (or scoped gates if `$scope` is provided). +- Report results. No side effects — this skill only reads and reports. + +## Graceful Degradation + +- If a gate command is not available (e.g., no test script in package.json), skip that gate and report: "Tests: SKIPPED — no test command found." +- If [quality-standards](../../../.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) directory is not found, warn and run only detectable gates (lint, type check, tests from package.json scripts). +- If no quality-related scripts are found at all, report: "No quality gates detected. Configure quality gate commands in package.json or way-of-working.md." + +## Notes + +- This skill is **read-only with side effects limited to running existing commands** — it never modifies source code or configuration. +- Two sources: [way-of-working.md](../../../.pair/adoption/tech/way-of-working.md) for the project-specific quality gate command (adoption-driven), [quality-standards](../../../.pair/knowledge/guidelines/quality-assurance/quality-standards/README.md) for universal quality standards. +- Each gate is independent — a failure in one gate does not prevent checking subsequent gates. +- Re-invoke after fixes to confirm resolution. Already-passing gates are re-verified but complete instantly. diff --git a/packages/knowledge-hub/dataset/.skills/process/implement/SKILL.md b/packages/knowledge-hub/dataset/.skills/process/implement/SKILL.md new file mode 100644 index 00000000..9a307447 --- /dev/null +++ b/packages/knowledge-hub/dataset/.skills/process/implement/SKILL.md @@ -0,0 +1,286 @@ +--- +name: implement +description: >- + Implements a user story by iterating through its tasks one at a time, following + a structured 5-step cycle per task. Composes /verify-quality and + /record-decision. Reads adoption files for project-specific decisions. Creates + a PR at story completion. +--- + +# /implement — Task Implementation + +Implement a user story by processing its tasks sequentially. Each task follows a 5-step cycle: context → branch → implementation → quality → commit. The story-level process has 4 phases (0–3). Creates a single PR when all tasks are done. + +## Composed Skills + +| Skill | Type | Required | +|-------|------|----------| +| `/verify-quality` | Capability | Yes — invoked at quality validation phase | +| `/record-decision` | Capability | Yes — invoked when a decision needs recording | +| `/assess-stack` | Capability | Optional — invoked when a new dependency is detected. If not installed, warn and continue. | +| `/verify-adoption` | Capability | Optional — invoked before commit to check adoption compliance. If not installed, warn and continue. | + +## Phase 0: Story & Task Analysis (BLOCKING) + +**No implementation without complete understanding.** + +### Step 0.1: Load Story + +1. **Check**: Is the user story already loaded in this session? +2. **Skip**: If yes, confirm story ID and move to Step 0.2. +3. **Act**: Read the story from the PM tool (per [way-of-working.md](../../../.pair/adoption/tech/way-of-working.md)). + - Understand business value and acceptance criteria. + - Verify status is "In Progress" and assigned to the developer. + - Confirm epic context. +4. **Verify**: Story is fully loaded. If not → **HALT**. + +### Step 0.2: Analyze Tasks + +1. **Check**: Are all tasks in the story readable and complete? +2. **Act**: Read ALL tasks. For each task, validate it has: + - Complete task information (ID, parent story, priority, status) + - Implementation approach (technical design, files, dependencies) + - Acceptance criteria (deliverable, quality standards, verification) + - Development workflow (TDD approach if development task, implementation steps) +3. **Verify**: All tasks are complete and follow the task template. If any task is incomplete → **HALT** and propose specific task updates. + +### Step 0.3: Confirm with Developer + +Present analysis: + +``` +IMPLEMENTATION STATE: +├── Story: [#ID: Title] +├── Tasks: [N total — list each with type and status] +├── Task Types: [Development: N, Documentation: N, Configuration: N] +├── Dependencies: [prerequisite stories and their status] +└── Ready: [Yes | No — reason] +``` + +Ask: _"Ready to proceed with implementation?"_ + +## Phase 1: Setup + +### Step 1.1: Load Technical Context + +1. **Check**: Are adoption files already loaded in this session? +2. **Skip**: If yes, move to Step 1.2. +3. **Act**: Read: + - [architecture.md](../../../.pair/adoption/tech/architecture.md) — architectural patterns + - [tech-stack.md](../../../.pair/adoption/tech/tech-stack.md) — approved libraries and versions + - [way-of-working.md](../../../.pair/adoption/tech/way-of-working.md) — development process +4. **Verify**: Technical context loaded. If adoption files missing, warn and proceed with guideline defaults. + +### Step 1.2: Create or Switch to Feature Branch + +1. **Check**: Does a branch for this story already exist? (`git branch --list 'feature/#-*'`) +2. **Skip**: If branch exists, switch to it (`git checkout `) and move to Step 1.3. +3. **Act**: Create branch from main: + ``` + git checkout main && git pull origin main + git checkout -b feature/#- + ``` +4. **Verify**: On the correct feature branch. + +### Step 1.3: Choose Commit Strategy + +1. **Check**: Is this a single-task story? +2. **Skip**: If single task, set strategy to `commit-per-story` (one task = one commit). Move to Phase 2. +3. **Act**: Ask the developer: + > **Commit strategy for this story:** + > 1. **Commit per task** (recommended) — one commit per completed task, granular git history, single PR at end + > 2. **Commit per story** — all tasks in one commit at the end, single PR +4. **Verify**: Strategy is set. Apply consistently for the entire story. + +## Phase 2: Task-by-Task Implementation + +Process tasks **sequentially**, one at a time. For each task: + +### Step 2.1: Select Next Task + +1. **Check**: Scan all tasks in dependency order. Find the first task that is not yet completed. + - A task is "completed" if its checklist item is marked ✅ in the story AND (if commit-per-task) the commit exists on the branch. +2. **Skip**: If all tasks are completed, move to Phase 3. +3. **Act**: Set the active task. Update session state: + ``` + ACTIVE TASK: + ├── Task: [T-N: Title] + ├── Type: [Development | Documentation | Configuration | Research] + ├── Mode: [TDD | Direct Implementation] + └── Phase: [Starting] + ``` + +### Step 2.2: Validate Task Completeness + +1. **Check**: Does the active task have all required fields per the task template? +2. **Skip**: If complete, proceed to Step 2.3. +3. **Act**: If incomplete → **HALT**. Report missing fields and propose specific updates. + +### Step 2.3: Execute Implementation + +**For Development Tasks (TDD Required):** + +Follow the TDD discipline rules strictly: + +**TDD Discipline Rules:** + +1. **New features → add tests autonomously.** Write unit tests without asking. Every new module file MUST have a corresponding unit test file (1:1 mapping). +2. **Modifying existing tests → ask developer with evidence.** Show what changes and why, get approval before modifying any existing test. +3. **No code+test changes in the same session.** When changing production code, do NOT modify tests until all existing tests pass. Separate RED, GREEN, and REFACTOR into distinct sessions: + - **RED session**: Write or modify ONLY test code. Tests MUST fail. No implementation code changes. + - **GREEN session**: Write or modify ONLY implementation code. Write minimal code to make tests pass. No test code changes. + - **REFACTOR session**: Improve structure without changing behavior. Both test and production code may be cleaned up. All tests must remain green. +4. **Every module file must have a corresponding unit test file.** 1:1 mapping between source modules and test files. +5. **Avoid mocks — prefer in-memory test doubles.** Use dependency injection with in-memory implementations (e.g., `InMemoryFileSystemService` instead of mocking `fs`). + +**For Non-Development Tasks (Direct Implementation):** + +- **Documentation**: Implement directly following documentation standards. +- **Configuration**: Apply infrastructure guidelines. +- **Research**: Document findings and recommendations. + +### Step 2.4: Check for New Dependencies + +1. **Check**: Did the implementation introduce any new dependency not listed in [tech-stack.md](../../../.pair/adoption/tech/tech-stack.md)? +2. **Skip**: If no new dependencies, move to Step 2.5. +3. **Act**: Is `/assess-stack` installed? + - **Yes**: Compose `/assess-stack` to validate and register the dependency. If `/assess-stack` rejects (incompatible) → **HALT**. + - **No**: Warn the developer: + > New dependency detected: `[package@version]`. `/assess-stack` is not installed — please manually verify against the tech stack and update [tech-stack.md](../../../.pair/adoption/tech/tech-stack.md). +4. **Verify**: Dependency is either validated by `/assess-stack` or acknowledged by developer. + +### Step 2.5: Check for Decisions + +1. **Check**: Did the implementation introduce any decision not covered by existing ADRs or ADLs? +2. **Skip**: If no new decisions needed, move to Step 2.6. +3. **Act**: Ask the developer if a decision record is needed. If yes, compose `/record-decision` with the appropriate `$type` (`architectural` or `non-architectural`) and `$topic`. +4. **Verify**: Decision recorded and adoption files updated. + +### Step 2.6: Verify Adoption Compliance + +1. **Check**: Is `/verify-adoption` installed? +2. **Skip**: If not installed, warn: + > `/verify-adoption` is not installed — skipping adoption compliance check. Please manually verify code against adoption files. + Move to Step 2.7. +3. **Act**: Compose `/verify-adoption` with `$scope` appropriate to the task. + - Non-conformities reported → resolve via `/assess-stack` (tech-stack issues) or `/record-decision` (architectural gaps). +4. **Verify**: Adoption compliance confirmed or all non-conformities resolved. + +### Step 2.7: Verify Quality + +1. **Act**: Compose `/verify-quality` with `$scope = all`. +2. **Verify**: All quality gates pass. If any gate fails → **HALT**. Developer must fix before proceeding. + +### Step 2.8: Commit (if commit-per-task) + +1. **Check**: Is the commit strategy `commit-per-task`? +2. **Skip**: If `commit-per-story`, mark task as complete in session state and return to Step 2.1. +3. **Act**: Stage and commit following the [commit template](../../../.pair/knowledge/guidelines/collaboration/templates/commit-template.md): + ``` + [#] : + + - + - Task: T-N — + + Refs: # + ``` +4. **Verify**: Commit created. Mark task as ✅ in story. Return to Step 2.1. + +## Phase 3: Final Commit and PR + +### Step 3.1: Final Commit (if commit-per-story) + +1. **Check**: Is the commit strategy `commit-per-story`? +2. **Skip**: If `commit-per-task`, all commits already exist. Move to Step 3.2. +3. **Act**: Stage all changes and commit: + ``` + [#] feat: + + - + - Tasks: T-1, T-2, ..., T-N + + Refs: # + ``` +4. **Verify**: Commit created with all changes. + +### Step 3.2: Push Branch + +1. **Check**: Is the branch already pushed and up to date with remote? +2. **Skip**: If up to date, move to Step 3.3. +3. **Act**: Push the branch: + ``` + git push -u origin feature/#- + ``` +4. **Verify**: Branch pushed to remote. + +### Step 3.3: Create or Update PR + +1. **Check**: Does a PR already exist for this branch? +2. **Skip**: If PR exists, update its description and move to output. +3. **Act**: Create PR following the [PR template](../../../.pair/knowledge/guidelines/collaboration/templates/pr-template.md): + - **Title**: `[#] : ` + - **Body**: Fill the PR template sections: + - Summary: what changed and why (from story statement) + - Story Context: link to user story issue, AC coverage + - Changes Made: list of all completed tasks and files affected + - Testing: test coverage and validation (from /verify-quality output) + - **Link**: Reference the user story issue (`Closes #`) + - **Labels**: Apply appropriate labels +4. **Verify**: PR created with complete description. + +## Output Format + +At completion: + +``` +IMPLEMENTATION COMPLETE: +├── Story: [#ID: Title] +├── Branch: [feature/#ID-description] +├── Strategy: [commit-per-task | commit-per-story] +├── Tasks: [N/N completed] +├── Commits: [N commits on branch] +├── PR: [#PR-number — URL] +└── Quality: [All gates passing] +``` + +## HALT Conditions + +Implementation stops immediately when: + +- **Story not loaded or incomplete** (Phase 0) +- **Task specifications incomplete** (Step 2.2) +- **Quality gate failure** (Step 2.7) — developer must fix +- **New dependency rejected by /assess-stack** (Step 2.4) +- **PR template not found** (Step 3.3) — cannot create PR without template +- **Commit template not found** (Step 2.8 / Step 3.1) — cannot commit without template + +On HALT: report the blocker clearly, propose resolution, wait for developer. + +## Idempotent Re-invocation + +Re-invoking `/implement` on a partially completed story is safe and expected: + +1. **Branch**: detects existing branch, switches to it. +2. **Commit strategy**: if commits already exist on branch, infer strategy from history. +3. **Tasks**: scans task checklist and git log to identify completed tasks. Skips them. +4. **PR**: detects existing PR, updates instead of creating duplicate. +5. **Quality gates**: re-runs all gates (fast if already passing). + +The skill resumes from the first incomplete step — never re-does completed work. + +## Graceful Degradation + +- **PM tool not accessible**: Ask developer to manually provide story details and task list. +- **Missing adoption files**: Warn and proceed with guideline defaults. +- **/assess-stack not installed**: Warn on new dependency, continue without validation. +- **/verify-adoption not installed**: Warn, skip adoption compliance check. +- **No quality gate command**: Fall back to individual checks (lint, test, type check). + +## Notes + +- This skill **modifies files and creates git artifacts** (branches, commits, PRs). +- Task iteration is sequential — each task completes its full cycle before the next begins. +- The developer can stop between tasks. Re-invoke to resume (idempotency ensures correct state). +- Single PR per story regardless of commit strategy. +- Commit messages follow the [commit template](../../../.pair/knowledge/guidelines/collaboration/templates/commit-template.md). +- PR description follows the [PR template](../../../.pair/knowledge/guidelines/collaboration/templates/pr-template.md).