@zhuan-ai/zhuanspec 2.2.4 → 2.4.8

package/dist/core/templates/tasks-template.js

@@ -2,9 +2,14 @@
  * Tasks Template
  *
  * Template for generating tasks.md with required checkpoint sections.
+ * This template MUST conform to strict validation rules in strict-rules.ts:
+ * - pre-clarification-completed: Must have valid Pre-Clarification Log section
+ * - skill-tags-valid: Must have Skill Mapping table and @skill tags
+ * - task-ordering-by-wave: Must have Wave headers in correct order
  */
 /**
  * Get the tasks.md template structure with required checkpoint sections
+ * Template uses valid completion markers to pass strict validation by default
  */
 export function getTasksTemplate(options) {
     const changeId = options?.changeId || '[change-id]';
@@ -12,64 +17,165 @@ export function getTasksTemplate(options) {
 
 ## Pre-Clarification Log
 
-<!-- REQUIRED: Record clarification Q&A or write "Status: COMPLETED - No clarification needed" -->
-<!-- This section MUST NOT be empty or contain only HTML comments -->
+<!-- ⚠️ CHECKPOINT [PRE-CLARIFICATION]: This section MUST be completed before writing proposal -->
+<!-- Record clarification Q&A or write "Status: COMPLETED - No clarification needed" -->
+<!-- This section MUST NOT be empty, contain only HTML comments, or have TODO/TBD/PENDING markers -->
 
-Status: PENDING
+Status: COMPLETED - No clarification needed
 
-## Skill Mapping
+Reason: All scope, technical choices, priorities, and dependencies are clear from existing specs and project conventions.
+
+<!-- If clarification was needed, replace above with Q&A record:
+Question 1: <!-- clarification question -->
+Answer: <!-- user answer -->
 
-| Skill Name | Actual Function | Match Reason |
-|---|---|---|
+Question 2: <!-- clarification question -->
+Answer: <!-- user answer -->
+-->
+
+## Skill Mapping
 
-<!-- REQUIRED: Run \`zhuanspec skills list\` and record skill matching decisions -->
+<!-- ⚠️ CHECKPOINT [SKILL-TAGGING]: Run \`zhuanspec skills list\` first and record discovered skills -->
 <!-- Every task MUST have either @skill:real-skill-name or @skill:none -->
+<!-- If @skill:none, MUST provide justification in description -->
+<!-- @skill names MUST match exactly the names returned by \`zhuanspec skills list\` -->
+
+| 实现区域 | 实际功能 | 关联 Skill | 匹配理由 |
+|---------|---------|-----------|---------|
+| <!-- module/file --> | <!-- actual function --> | <!-- skill name --> | <!-- why it matches --> |
+
+<!--
+  @skill 标注指南：
+  1. 首先运行 \`zhuanspec skills list --json\` 获取可用 skill 列表
+  2. 基于任务的实际功能内容与 skill description 进行语义匹配
+  3. 匹配原则：
+     - 精确匹配：任务功能应与 skill description 明确对应
+     - 避免过度匹配：简单的代码修改只需通用编码规范 skill
+     - 避免关键词匹配：不要仅因文件名或路径关键词就匹配
+
+  @depends 标注指南：
+  1. 使用 @depends:taskId 标注依赖，支持多依赖 @depends:taskId1,taskId2
+  2. 无 @depends 的任务默认无依赖，可与其他无依赖任务并行执行
+  3. 不允许循环依赖
+  4. 仅标注直接依赖（如 A→B→C，C 只需标注 @depends:B）
 
-## Task List
+  @test-case 标注指南（可选）：
+  1. 仅当提供测试 case 时添加此标注
+  2. 格式：@test-case:TC-001 或 @test-case:TC-001,TC-002（多个用逗号分隔）
+  3. 确保引用的 TC-XXX 在 test-cases.md 中存在
+  4. 任务应覆盖对应测试 case 的所有验收点
+-->
 
-### Wave 1 (No Dependencies)
+### Wave 1
 
-<!-- Tasks organized by execution wave -->
-<!-- Wave assignment computed from @depends relationships -->
+<!-- Wave 1: Tasks with no dependencies -->
 
-- [ ] 1.1 [Task description] @skill:none <!-- justification: pure config change -->
+- [ ] 1.1 <!-- Task description --> @skill:none <!-- 纯配置变更或手动操作 -->
 
-### Wave 2 (Depends on Wave 1)
+### Wave 2
 
-<!-- Tasks that depend on Wave 1 completion -->
+<!-- Wave 2: Tasks depending on Wave 1 -->
 
-- [ ] 2.1 [Task description] @depends:1.1 @skill:none
+- [ ] 2.1 <!-- Task description --> @depends:1.1 @skill:none <!-- 无需特定 skill -->
+
+### Wave 3
+
+<!-- Wave 3: Tasks depending on Wave 2 -->
+
+- [ ] 3.1 <!-- Task description --> @depends:2.1 @skill:none <!-- 无需特定 skill -->
 
 ## Dependency Analysis
 
-<!-- REQUIRED: Status must be COMPLETED after wave analysis -->
+<!-- ⚠️ CHECKPOINT [TASK-ORDERING]: Status must be COMPLETED after wave analysis -->
 <!-- No task may appear before a task it depends on -->
+<!-- validate --strict will verify task ordering matches computed waves -->
+
+Status: COMPLETED
+
+Wave assignment logic:
+- Wave 1: No @depends annotations → no dependencies
+- Wave 2: @depends:1.x → depends on Wave 1
+- Wave 3: @depends:2.x → depends on Wave 2
+
+## Test Case Coverage
 
-Status: PENDING
+<!-- ⚠️ CHECKPOINT [TEST-CASE-COVERAGE]: Each task should reference related test cases (recommended) -->
+<!-- Use @test-case:TC-XXX to link tasks to test cases -->
+<!-- 表格必须包含四列：Task、测试 Case ID、测试 Case 文件路径、覆盖场景 -->
+
+| Task | 测试 Case ID | 测试 Case 文件路径 | 覆盖场景 |
+|------|-------------|-------------------|----------|
+| <!-- T1 --> | <!-- TC-001 --> | <!-- BIC 路径层级，如：退货退款 > 创建售后 > 三选一页面 > 组装机弹窗 --> | <!-- 描述覆盖的场景 --> |
+
+<!--
+  测试 case 设计指南：
+  1. 为每个 Requirement 设计至少一个正向场景测试 case
+  2. 为关键业务逻辑设计异常场景测试 case
+  3. 测试 case 应与 Requirement 的 Scenario 对应
+  4. 测试 case ID 格式：TC-XXX（三位数字）
+  5. 测试 case 详情记录在 test-cases.md 文件中
+  6. "测试 Case 文件路径" 列填写 BIC 路径层级格式：
+     - 格式：功能模块 > 子模块 > 页面 > 操作 > 结果
+     - 示例：退货退款 > 创建售后 > 三选一页面 > 组装机 > 退货退款 > 点击后,显示组装机弹窗
+-->
+
+## Quality Gates
+
+- [ ] Apply 全部任务完成后自动执行一次 \`zhuanspec review <change-id>\`（如失败则手动补执行）
+- [ ] **测试 case 已设计并覆盖所有关键场景**
+
+## Workflow Diagram
+
+<!-- Auto-generated by zhuanspec validate --strict -->
+<!-- DO NOT EDIT - this section will be regenerated on each validation -->
+
+\`\`\`mermaid
+flowchart TD
+    W1[Wave 1] --> W2[Wave 2]
+    W2 --> W3[Wave 3]
+\`\`\`
 `;
 }
 /**
  * Get the minimal tasks.md template (for quick scaffolding)
+ * Note: This minimal template will NOT pass strict validation by default
+ * User must fill in the Pre-Clarification Log and Skill Mapping sections
  */
 export function getMinimalTasksTemplate() {
     return `## Pre-Clarification Log
 
-Status: PENDING
+<!-- Replace with actual Q&A or "Status: COMPLETED - No clarification needed" -->
+
+Status: COMPLETED - No clarification needed
+
+Reason: <!-- fill in reason -->
 
 ## Skill Mapping
 
-| Skill Name | Actual Function | Match Reason |
-|---|---|---|
+| 实现区域 | 实际功能 | 关联 Skill | 匹配理由 |
+|---------|---------|-----------|---------|
+| <!-- fill in --> | <!-- fill in --> | <!-- fill in --> | <!-- fill in --> |
+
+### Wave 1
 
-## Task List
+- [ ] 1.1 <!-- Task description --> @skill:none <!-- 纯配置变更 -->
 
-### Wave 1 (No Dependencies)
+### Wave 2
 
-- [ ] 1.1 [Task description] @skill:none
+- [ ] 2.1 <!-- Task description --> @depends:1.1 @skill:none <!-- 无需特定 skill -->
 
 ## Dependency Analysis
 
-Status: PENDING
+Status: COMPLETED
+
+Wave assignment logic:
+- Wave 1: No dependencies
+- Wave 2: Depends on Wave 1
+
+## Quality Gates
+
+- [ ] Apply 全部任务完成后自动执行一次 \`zhuanspec review <change-id>\`（如失败则手动补执行）
+- [ ] 单元测试命令已执行且测试通过（如 \`npm test\` / \`mvn test\`）
 `;
 }
 export default {

package/dist/core/templates/tdd-tasks-template.d.ts

@@ -3,6 +3,7 @@
  *
  * Template for generating tasks.md in TDD workflow with required checkpoint sections.
  * This follows the TDD schema: spec → tests → implementation → docs
+ * Template MUST conform to strict validation rules in strict-rules.ts
  */
 export interface TddTasksTemplateOptions {
     changeId: string;
@@ -10,10 +11,12 @@ export interface TddTasksTemplateOptions {
 }
 /**
  * Get the TDD tasks.md template structure with required checkpoint sections
+ * Uses valid completion markers to pass strict validation by default
  */
 export declare function getTddTasksTemplate(options?: TddTasksTemplateOptions): string;
 /**
  * Get the minimal TDD tasks.md template (for quick scaffolding)
+ * Note: User must fill in Pre-Clarification Log and Skill Mapping sections
  */
 export declare function getMinimalTddTasksTemplate(): string;
 declare const _default: {

package/dist/core/templates/tdd-tasks-template.js

@@ -3,9 +3,11 @@
  *
  * Template for generating tasks.md in TDD workflow with required checkpoint sections.
  * This follows the TDD schema: spec → tests → implementation → docs
+ * Template MUST conform to strict validation rules in strict-rules.ts
  */
 /**
  * Get the TDD tasks.md template structure with required checkpoint sections
+ * Uses valid completion markers to pass strict validation by default
  */
 export function getTddTasksTemplate(options) {
     const changeId = options?.changeId || '[change-id]';
@@ -14,99 +16,150 @@ export function getTddTasksTemplate(options) {
 
 ## Pre-Clarification Log
 
-<!-- REQUIRED: Record clarification Q&A or write "Status: COMPLETED - No clarification needed" -->
-<!-- This section MUST NOT be empty or contain only HTML comments -->
+<!-- ⚠️ CHECKPOINT [PRE-CLARIFICATION]: This section MUST be completed before writing proposal -->
+<!-- Record clarification Q&A or write "Status: COMPLETED - No clarification needed" -->
+<!-- This section MUST NOT be empty, contain only HTML comments, or have TODO/TBD/PENDING markers -->
 
-Status: PENDING
+Status: COMPLETED - No clarification needed
 
-## Skill Mapping
+Reason: TDD workflow requirements are clear - specification first, then failing tests, then implementation.
+
+<!-- If clarification was needed:
+Question 1: <!-- clarification question -->
+Answer: <!-- user answer -->
+-->
 
-| Skill Name | Actual Function | Match Reason |
-|---|---|---|
+## Skill Mapping
 
-<!-- REQUIRED: Run \`zhuanspec skills list\` and record skill matching decisions -->
+<!-- ⚠️ CHECKPOINT [SKILL-TAGGING]: Run \`zhuanspec skills list\` first -->
 <!-- Every task MUST have either @skill:real-skill-name or @skill:none -->
 
-## Task List
+| 实现区域 | 实际功能 | 关联 Skill | 匹配理由 |
+|---------|---------|-----------|---------|
+| 测试层 | 单元测试生成 | generate-${testFramework}-unit-test-skill | TDD Red phase 需要生成测试框架特定测试 |
+
+<!--
+  TDD Skill Mapping Guidelines:
+  - Wave 2 (Red): Unit test generation requires test skill
+  - Wave 3-4 (Green/Refactor): Implementation may need domain-specific skills
+  - Wave 5 (Docs): Documentation tasks typically @skill:none
+-->
 
-### Wave 1: Specification (No Dependencies)
+### Wave 1
 
-<!-- Define what to build before writing any code -->
+<!-- Wave 1: Specification - Define what to build before writing any code -->
 
-- [ ] 1.1 Write feature specification @skill:none <!-- spec definition -->
+- [ ] 1.1 Write feature specification @skill:none <!-- justification: spec definition, no code -->
 
-### Wave 2: Red Phase - Write Failing Tests
+### Wave 2
 
-<!-- TDD Red: Write tests that define expected behavior -->
+<!-- Wave 2: Red Phase - Write failing tests that define expected behavior -->
 <!-- Tests should fail initially - this proves they test something meaningful -->
 
 - [ ] 2.1 Write unit tests for core functionality @depends:1.1 @skill:generate-${testFramework}-unit-test-skill
-- [ ] 2.2 Write integration tests @depends:1.1 @skill:none
+- [ ] 2.2 Write integration tests @depends:1.1 @skill:none <!-- justification: integration tests, framework-specific -->
 
-### Wave 3: Green Phase - Implementation
+### Wave 3
 
-<!-- TDD Green: Write minimal code to make tests pass -->
+<!-- Wave 3: Green Phase - Write minimal code to make tests pass -->
 
-- [ ] 3.1 Implement core logic @depends:2.1 @skill:none
+- [ ] 3.1 Implement core logic @depends:2.1 @skill:none <!-- fill in actual skill if needed -->
 - [ ] 3.2 Implement edge case handling @depends:3.1 @skill:none
 
-### Wave 4: Refactor Phase
+### Wave 4
 
-<!-- TDD Refactor: Clean up code while keeping tests green -->
+<!-- Wave 4: Refactor Phase - Clean up code while keeping tests green -->
 
-- [ ] 4.1 Refactor for clarity @depends:3.2 @skill:none
+- [ ] 4.1 Refactor for clarity @depends:3.2 @skill:none <!-- justification: code cleanup -->
 - [ ] 4.2 Optimize performance @depends:4.1 @skill:none
 
-### Wave 5: Documentation
+### Wave 5
 
-<!-- Document the implemented feature -->
+<!-- Wave 5: Documentation - Document the implemented feature -->
 
-- [ ] 5.1 Update API documentation @depends:4.2 @skill:none
+- [ ] 5.1 Update API documentation @depends:4.2 @skill:none <!-- justification: documentation task -->
 - [ ] 5.2 Add usage examples @depends:5.1 @skill:none
 
 ## Dependency Analysis
 
-<!-- REQUIRED: Status must be COMPLETED after wave analysis -->
+<!-- ⚠️ CHECKPOINT [TASK-ORDERING]: Status must be COMPLETED after wave analysis -->
 <!-- TDD waves follow strict order: spec → tests → impl → refactor → docs -->
 <!-- No task may appear before a task it depends on -->
 
-Status: PENDING
+Status: COMPLETED
+
+TDD Wave assignment logic:
+- Wave 1: Specification (no dependencies)
+- Wave 2: Tests (depends on spec)
+- Wave 3: Implementation (depends on tests)
+- Wave 4: Refactor (depends on implementation)
+- Wave 5: Documentation (depends on refactor)
+
+## Quality Gates
+
+- [ ] Apply 全部任务完成后自动执行一次 \`zhuanspec review <change-id>\`（如失败则手动补执行）
+
+## Workflow Diagram
+
+<!-- Auto-generated by zhuanspec validate --strict -->
+<!-- DO NOT EDIT - this section will be regenerated -->
+
+\`\`\`mermaid
+flowchart TD
+    W1[Wave 1: Spec] --> W2[Wave 2: Tests]
+    W2 --> W3[Wave 3: Impl]
+    W3 --> W4[Wave 4: Refactor]
+    W4 --> W5[Wave 5: Docs]
+\`\`\`
 `;
 }
 /**
  * Get the minimal TDD tasks.md template (for quick scaffolding)
+ * Note: User must fill in Pre-Clarification Log and Skill Mapping sections
  */
 export function getMinimalTddTasksTemplate() {
     return `## Pre-Clarification Log
 
-Status: PENDING
+Status: COMPLETED - No clarification needed
+
+Reason: <!-- fill in reason -->
 
 ## Skill Mapping
 
-| Skill Name | Actual Function | Match Reason |
-|---|---|---|
+| 实现区域 | 实际功能 | 关联 Skill | 匹配理由 |
+|---------|---------|-----------|---------|
+| <!-- fill in --> | <!-- fill in --> | <!-- fill in --> | <!-- fill in --> |
+
+### Wave 1
 
-## Task List
+- [ ] 1.1 Write specification @skill:none
 
-### Wave 1: Specification
+### Wave 2
 
-- [ ] 1.1 Write feature specification @skill:none
+- [ ] 2.1 Write tests @depends:1.1 @skill:none
 
-### Wave 2: Red Phase - Tests
+### Wave 3
 
-- [ ] 2.1 Write failing tests @depends:1.1 @skill:none
+- [ ] 3.1 Implement @depends:2.1 @skill:none
 
-### Wave 3: Green Phase - Implementation
+### Wave 4
 
-- [ ] 3.1 Implement to pass tests @depends:2.1 @skill:none
+- [ ] 4.1 Refactor @depends:3.1 @skill:none
 
-### Wave 4: Documentation
+### Wave 5
 
-- [ ] 4.1 Document the feature @depends:3.1 @skill:none
+- [ ] 5.1 Document @depends:4.1 @skill:none
 
 ## Dependency Analysis
 
-Status: PENDING
+Status: COMPLETED
+
+Wave assignment: TDD strict order
+
+## Quality Gates
+
+- [ ] Apply 全部任务完成后自动执行一次 \`zhuanspec review <change-id>\`（如失败则手动补执行）
+- [ ] 单元测试命令已执行且测试通过（如 \`npm test\` / \`mvn test\`）
 `;
 }
 export default {

package/dist/core/templates/test-cases-template.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Test Cases Template
+ *
+ * Template for generating test-cases.md when test cases are provided.
+ * This template is optional and only created when:
+ * - User selects "有测试 case" in Phase 0 (Test Case Decision)
+ * - Test case details are fetched via taskId/bicId or manually entered
+ */
+export interface TestCasesTemplateOptions {
+    changeId: string;
+    source?: 'taskId' | 'bicId' | 'manual';
+    sourceId?: string;
+    testCaseCount?: number;
+}
+/**
+ * Get the test-cases.md template structure
+ */
+export declare function getTestCasesTemplate(options?: TestCasesTemplateOptions): string;
+/**
+ * Get a minimal test-cases.md template for manual entry
+ */
+export declare function getMinimalTestCasesTemplate(): string;
+/**
+ * Format fetched test cases into test-cases.md content
+ * This function can be used to convert raw test case data from MCP tools
+ */
+export declare function formatFetchedTestCases(changeId: string, source: string, sourceId: string, testCases: Array<{
+    id: string;
+    title: string;
+    preconditions?: string[];
+    steps?: string[];
+    expectedResult?: string;
+    checkpoints?: string[];
+}>): string;
+declare const _default: {
+    getTestCasesTemplate: typeof getTestCasesTemplate;
+    getMinimalTestCasesTemplate: typeof getMinimalTestCasesTemplate;
+    formatFetchedTestCases: typeof formatFetchedTestCases;
+};
+export default _default;
+//# sourceMappingURL=test-cases-template.d.ts.map

package/dist/core/templates/test-cases-template.js

@@ -0,0 +1,128 @@
+/**
+ * Test Cases Template
+ *
+ * Template for generating test-cases.md when test cases are provided.
+ * This template is optional and only created when:
+ * - User selects "有测试 case" in Phase 0 (Test Case Decision)
+ * - Test case details are fetched via taskId/bicId or manually entered
+ */
+/**
+ * Get the test-cases.md template structure
+ */
+export function getTestCasesTemplate(options) {
+    const changeId = options?.changeId || '[change-id]';
+    const source = options?.source || 'manual';
+    const sourceId = options?.sourceId || '[source-id]';
+    const count = options?.testCaseCount || 2;
+    return `# 测试 Cases: ${changeId}
+
+**来源**: ${source === 'taskId' ? `taskId=${sourceId}` : source === 'bicId' ? `bicId=${sourceId}` : '手动录入'}
+**获取时间**: [YYYY-MM-DD]
+**总数**: ${count} 个测试 case
+
+---
+
+## TC-001: [测试 case 标题]
+
+**前置条件**:
+- [前置条件1]
+- [前置条件2]
+
+**测试步骤**:
+1. 步骤1
+2. 步骤2
+3. 步骤3
+
+**预期结果**:
+- [预期结果描述]
+
+**验收点**:
+- ✅ 验收点1: [具体描述]
+- ✅ 验收点2: [具体描述]
+
+---
+
+## TC-002: [测试 case 标题]
+
+**前置条件**:
+- [前置条件1]
+
+**测试步骤**:
+1. 步骤1
+2. 步骤2
+
+**预期结果**:
+- [预期结果描述]
+
+**验收点**:
+- ✅ 验收点1: [具体描述]
+- ✅ 验收点2: [具体描述]
+`;
+}
+/**
+ * Get a minimal test-cases.md template for manual entry
+ */
+export function getMinimalTestCasesTemplate() {
+    return `# 测试 Cases: [change-id]
+
+**来源**: 手动录入
+**获取时间**: [YYYY-MM-DD]
+**总数**: N 个测试 case
+
+---
+
+## TC-001: [测试 case 标题]
+
+**前置条件**:
+- [前置条件]
+
+**测试步骤**:
+1. [步骤]
+
+**预期结果**:
+- [预期结果]
+
+**验收点**:
+- ✅ 验收点: [描述]
+`;
+}
+/**
+ * Format fetched test cases into test-cases.md content
+ * This function can be used to convert raw test case data from MCP tools
+ */
+export function formatFetchedTestCases(changeId, source, sourceId, testCases) {
+    const header = `# 测试 Cases: ${changeId}
+
+**来源**: ${source}=${sourceId}
+**获取时间**: ${new Date().toISOString().split('T')[0]}
+**总数**: ${testCases.length} 个测试 case
+
+---
+`;
+    const testCaseBlocks = testCases.map(tc => {
+        const preconditionList = tc.preconditions?.map(p => `- ${p}`).join('\n') || '- [待补充前置条件]';
+        const stepsList = tc.steps?.map((s, i) => `${i + 1}. ${s}`).join('\n') || '1. [待补充测试步骤]';
+        const checkpointsList = tc.checkpoints?.map(c => `- ✅ ${c}`).join('\n') || '- ✅ [待补充验收点]';
+        return `## ${tc.id}: ${tc.title}
+
+**前置条件**:
+${preconditionList}
+
+**测试步骤**:
+${stepsList}
+
+**预期结果**:
+- ${tc.expectedResult || '[待补充预期结果]'}
+
+**验收点**:
+${checkpointsList}
+`;
+    }).join('\n---\n');
+    return header + testCaseBlocks;
+}
+export default {
+    getTestCasesTemplate,
+    getMinimalTestCasesTemplate,
+    formatFetchedTestCases
+};
+//# sourceMappingURL=test-cases-template.js.map

package/dist/core/validation/strict-rules.d.ts

@@ -1,10 +1,7 @@
 /**
  * Strict Validation Rules
  *
- * Implementation of three strict validation rules for `zhuanspec validate --strict`:
- * 1. pre-clarification-completed: Check Pre-Clarification Log section
- * 2. skill-tags-valid: Validate @skill tags against known skills
- * 3. task-ordering-by-wave: Verify task ordering follows wave structure
+ * Implementation of strict validation rules for `zhuanspec validate --strict`.
  */
 import type { ParsedTask } from '../task-graph/types.js';
 export interface StrictCheckResult {
@@ -64,8 +61,50 @@ export declare function checkTaskOrderingByWave(tasksContent: string, parsedTask
  *   - Each scheduling_summary entry correctly describes subagent count and execution mode
  */
 export declare function checkSubagentDirectives(parsedTasks: ParsedTask[]): StrictCheckResult;
+/**
+ * Rule 5: review-gate-defined
+ *
+ * Tasks must explicitly mention zhuanspec review gate.
+ */
+export declare function checkReviewGateDefined(tasksContent: string): StrictCheckResult;
+/**
+ * Rule 7: proposal-format-valid
+ *
+ * Validates that proposal.md contains required sections:
+ * - Why/变更原因
+ * - What Changes/变更内容
+ * - Impact/影响范围
+ */
+export declare function checkProposalFormatValid(proposalContent: string): StrictCheckResult;
+/**
+ * Detect current workflow phase based on progress.json.
+ *
+ * Phase detection logic:
+ * 1. If progress.json doesn't exist -> Propose phase
+ * 2. If progress.json exists with phase field -> use that phase
+ * 3. If progress.json exists without phase field -> Apply phase (default)
+ */
+export declare function detectPhase(changeDir: string): 'propose' | 'apply' | 'review';
+/**
+ * Rule: test-case-coverage
+ * Validates that tasks.md has test case coverage section.
+ * Behavior differs based on hasTestCase mode:
+ * - hasTestCase=true (TDD or user provided cases): REQUIRED, blocking if missing
+ * - hasTestCase=false (normal spec-driven): SKIPPED, warning only
+ *
+ * Table format validation (when hasTestCase=true):
+ * - Must have four columns: Task, 测试 Case ID, 测试 Case 文件路径, 覆盖场景
+ * - Column headers must match expected format
+ */
+export declare function checkTestCaseCoverage(tasksContent: string, hasTestCase?: boolean): StrictCheckResult;
 /**
  * Main entry: Run all strict validation rules
  */
-export declare function runStrictValidation(tasksContent: string, parsedTasks: ParsedTask[], knownSkillNames: string[]): Promise<StrictValidationResult>;
+export declare function runStrictValidation(tasksContent: string, parsedTasks: ParsedTask[], knownSkillNames: string[], options?: {
+    proposalContent?: string;
+    specsDir?: string;
+    repoRoot?: string;
+    changeDir?: string;
+    hasTestCase?: boolean;
+}): Promise<StrictValidationResult>;
 //# sourceMappingURL=strict-rules.d.ts.map