ai-qakit 1.0.0

package/templates/.claude/doc-templates/test-summary-report.md

@@ -0,0 +1,401 @@
+# Test Summary Report Template
+
+## Standard Test Summary Report Format
+
+| Section | Description |
+|---------|-------------|
+| **Project Name** | Name of the project or module under test |
+| **Version / Release** | Version number, sprint, or release name |
+| **Prepared By** | QA responsible for the report |
+| **Date** | Report generation date |
+| **Objective** | Summary of what the testing aimed to validate |
+| **Scope of Testing** | Features, modules, or functions tested |
+| **Test Approach** | Testing method used (Manual, Automation, Exploratory) |
+| **Test Environment** | Environment details: URLs, browsers, OS, devices |
+| **Summary of Execution** | Overview of total tests and results |
+| **Defect Summary** | Overview of defects by severity and status |
+| **Metrics Summary** | High-level process metrics |
+| **Test Deliverables** | List of artifacts produced |
+| **Major Findings** | Notable issues, risks, or blockers |
+| **Recommendations** | Actions for improving quality |
+| **Sign-off Recommendation** | Go / No-Go decision and rationale |
+| **Approved By** | QA Lead / PM / PO |
+
+---
+
+## Test Summary Report Template
+
+```markdown
+# Test Summary Report: [Project/Feature Name]
+
+## 1. Document Information
+
+| Field | Value |
+|-------|-------|
+| **Project Name** | [Project name] |
+| **Version / Release** | [Version or Sprint name] |
+| **Prepared By** | [QA Lead name] |
+| **Date** | [Date] |
+| **Test Period** | [Start date] - [End date] |
+
+---
+
+## 2. Objective
+
+[Summary of what the testing aimed to validate in this cycle]
+
+---
+
+## 3. Scope of Testing
+
+### 3.1 Features Tested
+
+| Module / Feature | Test Coverage |
+|------------------|---------------|
+| [Feature 1] | [Coverage %] |
+| [Feature 2] | [Coverage %] |
+
+### 3.2 Features Not Tested
+
+| Module / Feature | Reason |
+|------------------|--------|
+| [Feature] | [Reason] |
+
+---
+
+## 4. Test Approach
+
+| Approach | Description |
+|----------|-------------|
+| **Manual Testing** | [Description] |
+| **Automation** | [Description] |
+| **Exploratory** | [Description] |
+
+---
+
+## 5. Test Environment
+
+| Field | Value |
+|-------|-------|
+| **Environment** | [Staging/Production] |
+| **URL** | [URL] |
+| **Browser(s)** | [Browser versions] |
+| **OS** | [Operating systems] |
+| **App Version** | [Version] |
+
+---
+
+## 6. Summary of Execution
+
+### 6.1 Test Execution Overview
+
+| Metric | Count | Percentage |
+|--------|-------|------------|
+| **Total Test Cases** | [X] | 100% |
+| **Executed** | [X] | [X]% |
+| **Passed** | [X] | [X]% |
+| **Failed** | [X] | [X]% |
+| **Blocked** | [X] | [X]% |
+| **Not Executed** | [X] | [X]% |
+
+### 6.2 Execution by Priority
+
+| Priority | Total | Passed | Failed | Blocked |
+|----------|-------|--------|--------|---------|
+| P0 (Critical) | [X] | [X] | [X] | [X] |
+| P1 (High) | [X] | [X] | [X] | [X] |
+| P2 (Medium) | [X] | [X] | [X] | [X] |
+| P3 (Low) | [X] | [X] | [X] | [X] |
+
+### 6.3 Execution by Module
+
+| Module | Total | Passed | Failed | Pass Rate |
+|--------|-------|--------|--------|-----------|
+| [Module 1] | [X] | [X] | [X] | [X]% |
+| [Module 2] | [X] | [X] | [X] | [X]% |
+
+---
+
+## 7. Defect Summary
+
+### 7.1 Defect Overview
+
+| Metric | Count |
+|--------|-------|
+| **Total Defects** | [X] |
+| **Open** | [X] |
+| **Fixed** | [X] |
+| **Verified** | [X] |
+| **Closed** | [X] |
+
+### 7.2 Defects by Severity
+
+| Severity | Total | Open | Fixed | Verified |
+|----------|-------|------|-------|----------|
+| Critical | [X] | [X] | [X] | [X] |
+| Major | [X] | [X] | [X] | [X] |
+| Minor | [X] | [X] | [X] | [X] |
+| Low | [X] | [X] | [X] | [X] |
+
+### 7.3 Open Defects (Blocking Release)
+
+| Bug ID | Title | Severity | Status | Owner |
+|--------|-------|----------|--------|-------|
+| [ID] | [Title] | [Severity] | [Status] | [Name] |
+
+---
+
+## 8. Metrics Summary
+
+| Metric | Value | Target | Status |
+|--------|-------|--------|--------|
+| **Test Execution Rate** | [X]% | >= 95% | ✅/❌ |
+| **Pass Rate** | [X]% | >= 90% | ✅/❌ |
+| **Blocked Rate** | [X]% | <= 5% | ✅/❌ |
+| **Defect Density** | [X] defects/TC | <= 0.2 | ✅/❌ |
+| **Critical/Major Open** | [X] | 0 | ✅/❌ |
+| **Environment Stability** | [X]% uptime | >= 95% | ✅/❌ |
+
+---
+
+## 9. Test Deliverables
+
+| Deliverable | Status | Location |
+|-------------|--------|----------|
+| Test Plan | Complete | [Link] |
+| Test Cases | Complete | [Link] |
+| Defect Log | Complete | [Link] |
+| Daily QA Reports | Complete | [Link] |
+| Test Summary Report | Complete | This document |
+
+---
+
+## 10. Major Findings / Observations
+
+### 10.1 Critical Issues
+
+1. [Issue description and impact]
+2. [Issue description and impact]
+
+### 10.2 Risks Identified
+
+| Risk | Impact | Mitigation |
+|------|--------|------------|
+| [Risk] | [Impact] | [Mitigation] |
+
+### 10.3 Blockers Encountered
+
+| Blocker | Duration | Resolution |
+|---------|----------|------------|
+| [Blocker] | [Hours/Days] | [How resolved] |
+
+---
+
+## 11. Recommendations
+
+### 11.1 For This Release
+
+1. [Recommendation 1]
+2. [Recommendation 2]
+
+### 11.2 For Future Releases
+
+1. [Recommendation 1]
+2. [Recommendation 2]
+
+---
+
+## 12. Sign-off Recommendation
+
+### Decision: **[GO / CONDITIONAL GO / NO-GO]**
+
+### Rationale
+
+[Explain the decision based on test results, open defects, and risk assessment]
+
+### Conditions (if Conditional Go)
+
+1. [Condition 1]
+2. [Condition 2]
+
+---
+
+## 13. Approval
+
+| Role | Name | Date | Decision |
+|------|------|------|----------|
+| QA Lead | [Name] | [Date] | [Go/No-Go] |
+| PM/PO | [Name] | [Date] | [Go/No-Go] |
+| Tech Lead | [Name] | [Date] | [Go/No-Go] |
+```
+
+---
+
+## Example Test Summary Report
+
+```markdown
+# Test Summary Report: Example Web Portal - Authentication Module
+
+## 1. Document Information
+
+| Field | Value |
+|-------|-------|
+| **Project Name** | Example Web Portal - Authentication Module |
+| **Version / Release** | Sprint 12 - Login Feature Enhancements |
+| **Prepared By** | Jordan Lee (QA Lead) |
+| **Date** | Nov 2, 2025 |
+| **Test Period** | Oct 26, 2025 - Nov 1, 2025 |
+
+---
+
+## 2. Objective
+
+Validate core authentication flows: login, logout, and password reset, ensuring stable integration and usability across browsers.
+
+---
+
+## 3. Scope of Testing
+
+### 3.1 Features Tested
+
+| Module / Feature | Test Coverage |
+|------------------|---------------|
+| Login | 100% |
+| Logout | 100% |
+| Password Reset | 95% |
+| Remember Me | 100% |
+| Session Timeout | 90% |
+
+### 3.2 Features Not Tested
+
+| Module / Feature | Reason |
+|------------------|--------|
+| Social Login | Planned for Sprint 14 |
+| 2FA | Not implemented |
+
+---
+
+## 6. Summary of Execution
+
+### 6.1 Test Execution Overview
+
+| Metric | Count | Percentage |
+|--------|-------|------------|
+| **Total Test Cases** | 80 | 100% |
+| **Executed** | 80 | 100% |
+| **Passed** | 74 | 92.5% |
+| **Failed** | 4 | 5% |
+| **Blocked** | 2 | 2.5% |
+
+---
+
+## 7. Defect Summary
+
+### 7.1 Defect Overview
+
+| Metric | Count |
+|--------|-------|
+| **Total Defects** | 10 |
+| **Open** | 0 |
+| **Fixed** | 7 |
+| **Verified** | 10 |
+| **Closed** | 10 |
+
+### 7.2 Defects by Severity
+
+| Severity | Total | Open | Fixed | Verified |
+|----------|-------|------|-------|----------|
+| Critical | 0 | 0 | 0 | 0 |
+| Major | 3 | 0 | 3 | 3 |
+| Minor | 5 | 0 | 5 | 5 |
+| Low | 2 | 0 | 2 | 2 |
+
+---
+
+## 8. Metrics Summary
+
+| Metric | Value | Target | Status |
+|--------|-------|--------|--------|
+| **Test Execution Rate** | 100% | >= 95% | ✅ |
+| **Pass Rate** | 92.5% | >= 90% | ✅ |
+| **Blocked Rate** | 2.5% | <= 5% | ✅ |
+| **Defect Density** | 0.125 | <= 0.2 | ✅ |
+| **Critical/Major Open** | 0 | 0 | ✅ |
+| **Environment Stability** | 97% | >= 95% | ✅ |
+
+---
+
+## 10. Major Findings / Observations
+
+### 10.1 Critical Issues
+
+1. Password reset email delayed due to SMTP queue (resolved)
+2. Minor UI alignment issues on Edge browser (fixed)
+
+### 10.2 Blockers Encountered
+
+| Blocker | Duration | Resolution |
+|---------|----------|------------|
+| Environment outage | 1 hour | DevOps restart |
+
+---
+
+## 11. Recommendations
+
+### 11.1 For This Release
+
+1. Monitor SMTP service performance post-release
+2. Add Edge browser to regression suite
+
+### 11.2 For Future Releases
+
+1. Optimize email trigger service
+2. Add uptime monitoring alert for staging
+
+---
+
+## 12. Sign-off Recommendation
+
+### Decision: **GO**
+
+### Rationale
+
+- No critical defects open
+- All major defects resolved and verified
+- Pass rate (92.5%) exceeds target (90%)
+- Core functionality stable across browsers
+- Acceptable risk level for release
+
+---
+
+## 13. Approval
+
+| Role | Name | Date | Decision |
+|------|------|------|----------|
+| QA Lead | Jordan Lee | Nov 2, 2025 | Go |
+| PM | Avery Chen | Nov 2, 2025 | Go |
+```
+
+---
+
+## Tips for Writing Good Test Summary Reports
+
+### DO's ✅
+
+- **Focus on insight, not just numbers** - explain what results mean
+- **Highlight risk areas** - mention modules needing more coverage
+- **Be transparent** - call out blockers and issues
+- **End with clear sign-off** - Go, Conditional Go, or No-Go
+- **Keep it visual** - charts and tables add clarity
+- **Link to evidence** - reference test cases, bugs, reports
+
+### DON'Ts ❌
+
+- Don't just list numbers without context
+- Don't hide problems - transparency builds trust
+- Don't skip recommendations
+- Don't leave sign-off ambiguous
+
+---
+
+_End of Test Summary Report Template_

package/templates/.claude/hooks/dev-rules-reminder.cjs

@@ -0,0 +1,101 @@
+#!/usr/bin/env node
+/**
+ * Development Rules Reminder - UserPromptSubmit Hook (Optimized)
+ *
+ * Injects context: session info, rules, and modularization reminders.
+ *
+ * Exit Codes:
+ *   0 - Success (non-blocking, allows continuation)
+ */
+
+const fs = require('fs');
+const os = require('os');
+const path = require('path');
+
+// ═══════════════════════════════════════════════════════════════════════════
+// HELPER FUNCTIONS
+// ═══════════════════════════════════════════════════════════════════════════
+
+function resolveWorkflowPath(filename) {
+  const localPath = path.join(process.cwd(), '.claude', 'workflows', filename);
+  const globalPath = path.join(os.homedir(), '.claude', 'workflows', filename);
+  if (fs.existsSync(localPath)) return `.claude/workflows/${filename}`;
+  if (fs.existsSync(globalPath)) return `~/.claude/workflows/${filename}`;
+  return null;
+}
+
+function resolveScriptPath(filename) {
+  const localPath = path.join(process.cwd(), '.claude', 'scripts', filename);
+  const globalPath = path.join(os.homedir(), '.claude', 'scripts', filename);
+  if (fs.existsSync(localPath)) return `.claude/scripts/${filename}`;
+  if (fs.existsSync(globalPath)) return `~/.claude/scripts/${filename}`;
+  return null;
+}
+
+function wasRecentlyInjected(transcriptPath) {
+  try {
+    if (!transcriptPath || !fs.existsSync(transcriptPath)) return false;
+    const transcript = fs.readFileSync(transcriptPath, 'utf-8');
+    // Check last 150 lines (hook output is ~30 lines, so this covers ~5 user prompts)
+    return transcript.split('\n').slice(-150).some(line => line.includes('[IMPORTANT] Consider Modularization'));
+  } catch (e) {
+    return false;
+  }
+}
+
+// ═══════════════════════════════════════════════════════════════════════════
+// REMINDER TEMPLATE
+// ═══════════════════════════════════════════════════════════════════════════
+
+function buildReminder({ devRulesPath, catalogScript }) {
+  return [
+    `## Rules`,
+    ...(devRulesPath ? [`- Read and follow development rules: "${devRulesPath}"`] : []),
+    `- Markdown files are organized in: Plans → "plans/" directory, Docs → "docs/" directory`,
+    `- **IMPORTANT:** DO NOT create markdown files out of "plans/" or "docs/" directories UNLESS the user explicitly requests it.`,
+    ...(catalogScript ? [
+      `- Activate skills: Run \`python ${catalogScript} --skills\` to generate a skills catalog and analyze it, then activate the relevant skills that are needed for the task during the process.`,
+      `- Execute commands: Run \`python ${catalogScript} --commands\` to generate a commands catalog and analyze it, then execute the relevant SlashCommands that are needed for the task during the process.`
+    ] : []),
+    `- When skills' scripts are failed to execute, always fix them and run again, repeat until success.`,
+    `- Follow **YAGNI (You Aren't Gonna Need It) - KISS (Keep It Simple, Stupid) - DRY (Don't Repeat Yourself)** principles`,
+    `- Sacrifice grammar for the sake of concision when writing reports.`,
+    `- In reports, list any unresolved questions at the end, if any.`,
+    `- IMPORTANT: Ensure token consumption efficiency while maintaining high quality.`,
+    ``,
+    `## **[IMPORTANT] Consider Modularization:**`,
+    `- Check existing modules before creating new`,
+    `- Analyze logical separation boundaries (functions, classes, concerns)`,
+    `- Use kebab-case naming with descriptive names, it's fine if the file name is long because this ensures file names are self-documenting for LLM tools (Grep, Glob, Search)`,
+    `- Write descriptive code comments`,
+    `- After modularization, continue with main task`,
+    `- When not to modularize: Markdown files, plain text files, bash scripts, configuration files, environment variables files, etc.`,
+  ];
+}
+
+// ═══════════════════════════════════════════════════════════════════════════
+// MAIN EXECUTION
+// ═══════════════════════════════════════════════════════════════════════════
+
+async function main() {
+  try {
+    const stdin = fs.readFileSync(0, 'utf-8').trim();
+    if (!stdin) process.exit(0);
+
+    const payload = JSON.parse(stdin);
+    if (wasRecentlyInjected(payload.transcript_path)) process.exit(0);
+
+    const devRulesPath = resolveWorkflowPath('development-rules.md');
+    const catalogScript = resolveScriptPath('generate_catalogs.py');
+
+    const output = buildReminder({ devRulesPath, catalogScript });
+
+    console.log(output.join('\n'));
+    process.exit(0);
+  } catch (error) {
+    console.error(`Dev rules hook error: ${error.message}`);
+    process.exit(0);
+  }
+}
+
+main();

package/templates/.claude/hooks/dev-rules-reminder.js

@@ -0,0 +1,96 @@
+#!/usr/bin/env node
+
+/**
+ * Development Rules Reminder - PreToolUse Hook
+ *
+ * Injects modularization reminders before Write/Edit operations.
+ * Uses transcript checking to inject only once per ~50 messages for token efficiency.
+ *
+ * Exit Codes:
+ *   0 - Success (non-blocking, allows continuation)
+ */
+
+import fs from 'fs';
+
+/**
+ * Check if reminder was recently injected by scanning transcript
+ */
+function wasRecentlyInjected(transcriptPath) {
+  try {
+    if (!transcriptPath || !fs.existsSync(transcriptPath)) {
+      // Transcript doesn't exist - inject reminder
+      return false;
+    }
+
+    const transcript = fs.readFileSync(transcriptPath, 'utf-8');
+    const lines = transcript.split('\n');
+
+    // Check last 50 lines for reminder marker
+    const recentLines = lines.slice(-50);
+    const wasInjected = recentLines.some(line => line.includes('**[IMPORTANT]** Consider Modularization'));
+
+    return wasInjected;
+
+  } catch (error) {
+    // If we can't read transcript, assume not injected (fail-open)
+    return false;
+  }
+}
+
+/**
+ * Main hook execution
+ */
+async function main() {
+  try {
+    // Read hook payload from stdin
+    const stdin = fs.readFileSync(0, 'utf-8').trim();
+
+    if (!stdin) {
+      process.exit(0);
+    }
+
+    const payload = JSON.parse(stdin);
+    const toolName = payload.tool_name;
+
+    // Check if reminder was recently injected
+    if (wasRecentlyInjected(payload.transcript_path)) {
+      process.exit(0);
+    }
+
+    const reminder = [
+      `## Rules`,
+      `- Read and follow development rules: ".claude/workflows/development-rules.md"`,
+      `- Read and follow documentation management: ".claude/workflows/documentation-management.md"`,
+      `- Markdown files are organized in: Plans → "plans/" directory, Docs → "docs/" directory`,
+      `- Report markdown files in the same directory as the plan file`,
+      `- IMPORTANT: DO NOT create markdown files out of "plans/" or "docs/" directories UNLESS the user explicitly requests it.`,
+      `- Activate skills: Run \`python .claude/scripts/generate_catalogs.py --skills\` to generate a skills catalog and analyze it, then activate the relevant skills that are needed for the task during the process.`,
+      `- Execute commands: Run \`python .claude/scripts/generate_catalogs.py --commands\` to generate a commands catalog and analyze it, then execute the relevant SlashCommands that are needed for the task during the process.`,
+      `- When skills' scripts are failed to execute, always fix them and run again, repeat until success.`,
+      `- Follow **YANGI (You Aren't Gonna Need It) - KISS (Keep It Simple, Stupid) - DRY (Don't Repeat Yourself)** principles`,
+      `- Sacrifice grammar for the sake of concision when writing reports.`,
+      `- In reports, list any unresolved questions at the end, if any.`,
+      `- IMPORTANT: Ensure token consumption efficiency while maintaining high quality.`,
+      `- IMPORTANT: Include these rules when prompting subagents to perform tasks.`,
+      ``,
+      `## **[IMPORTANT] Consider Modularization:**`,
+      `- Check existing modules before creating new`,
+      `- Analyze logical separation boundaries (functions, classes, concerns)`,
+      `- Use kebab-case naming with descriptive names, it's fine if the file name is long because this ensures file names are self-documenting for LLM tools (Grep, Glob, Search)`,
+      `- Write descriptive code comments`,
+      `- After modularization, continue with main task`,
+      `- When not to modularize: Markdown files, plain text files, bash scripts, configuration files, environment variables files, etc.`,
+      `- IMPORTANT: Include these considerations when prompting subagents to perform tasks.`,
+    ].join('\n');
+
+    console.log(reminder);
+    process.exit(0);
+
+  } catch (error) {
+    // Fail-open: log error but allow operation to continue
+    console.error(`Dev rules hook error: ${error.message}`);
+    process.exit(0);
+  }
+}
+
+main();

package/templates/.claude/hooks/executable_force-agent-skills-eval.sh

@@ -0,0 +1,38 @@
+#!/bin/bash
+# UserPromptSubmit hook that forces explicit delegation evaluation
+
+cat << 'EOF'
+📋 MANDATORY DELEGATION SEQUENCE
+
+**Execution Priority:**
+1. Specialized sub-agent (Task tool) → First choice
+2. Skill (Skill tool) → If no specialized agent
+3. general-purpose agent OR manual → Last resort
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Step 1 - EVALUATE AGENTS:
+Scan available subagent_types. For top matches: [agent] - YES/NO - [reason]
+
+Step 2 - EVALUATE SKILLS (only if no agent fits):
+Scan <available_skills>. For top matches: [skill] - YES/NO - [reason]
+
+Step 3 - ACTIVATE:
+- Agent YES → Task(subagent_type="agent-name") NOW
+  └─ Include in prompt: "Check <available_skills> and use Skill tool for matching tasks"
+- Skill YES → Skill("skill-name") NOW
+- Neither → general-purpose agent OR manual
+
+Step 4 - IMPLEMENT:
+Only after Step 3 is complete, proceed with implementation.
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+⚠️ INDEPENDENCE RULE: Each task MUST be self-contained—no dependencies on concurrent tasks.
+
+🔢 MAX CONCURRENT AGENTS: 3 parallel agents max. If >3 tasks, batch into waves.
+
+⚡ ORCHESTRATE, DON'T IMPLEMENT: Delegate to subagents. Review their work at the end.
+
+🔧 SUB-AGENT SKILL INHERITANCE: When delegating, instruct sub-agents to check <available_skills> and use Skill tool for matching tasks.
+EOF