@codewalla_india/openspec 1.3.2 → 1.3.3

package/README.md

@@ -1,272 +1,272 @@
-<p align="center">
-  <a href="https://github.com/codewalla-engineering/openspec-upstream-sync">
-    <picture>
-      <source srcset="assets/openspec_pixel_dark.svg" media="(prefers-color-scheme: dark)">
-      <source srcset="assets/openspec_pixel_light.svg" media="(prefers-color-scheme: light)">
-      <img src="assets/openspec_pixel_light.svg" alt="OpenSpec logo" height="64">
-    </picture>
-  </a>
-
-</p>
-<p align="center">Spec-driven development for AI coding assistants.</p>
-<p align="center">
-  <a href="https://github.com/codewalla-engineering/openspec-upstream-sync/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/codewalla-engineering/openspec-upstream-sync/actions/workflows/ci.yml/badge.svg" /></a>
-  <a href="https://www.npmjs.com/package/@codewalla_india/openspec"><img alt="npm version" src="https://img.shields.io/npm/v/@codewalla_india/openspec?style=flat-square" /></a>
-  <a href="https://nodejs.org/"><img alt="node version" src="https://img.shields.io/node/v/@codewalla_india/openspec?style=flat-square" /></a>
-  <a href="./LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" /></a>
-  <a href="https://conventionalcommits.org"><img alt="Conventional Commits" src="https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg?style=flat-square" /></a>
-  <a href="https://discord.gg/YctCnvvshC"><img alt="Discord" src="https://img.shields.io/badge/Discord-Join%20the%20community-5865F2?logo=discord&logoColor=white&style=flat-square" /></a>
-</p>
-
-<p align="center">
-  <img src="assets/openspec_dashboard.png" alt="OpenSpec dashboard preview" width="90%">
-</p>
-
-<p align="center">
-  Follow <a href="https://x.com/0xTab">@0xTab on X</a> for updates · Join the <a href="https://discord.gg/YctCnvvshC">OpenSpec Discord</a> for help and questions.
-</p>
-
-<p align="center">
-  <sub>🚀 <strong>New:</strong> <a href="docs/opsx.md">OPSX Workflow</a> — schema-driven, hackable, fluid. Iterate on workflows without code changes.</sub>
-</p>
-
-# OpenSpec
-
-OpenSpec aligns humans and AI coding assistants with spec-driven development so you agree on what to build before any code is written. **No API keys required.**
-
-## 🎯 Why OpenSpec?
-
-AI coding assistants are powerful but unpredictable when requirements live in chat history. OpenSpec adds a lightweight specification workflow that locks intent before implementation, giving you deterministic, reviewable outputs.
-
-Key outcomes:
-- Human and AI stakeholders agree on specs before work begins
-- Structured change folders (proposals, tasks, and spec updates) keep scope explicit and auditable
-- Shared visibility into what's proposed, active, or archived
-- Works with the AI tools you already use: custom slash commands where supported, context rules everywhere else
-
-## 🌟 What's New in v1.8.0
-
-### 🚀 OPSX Workflow - The New Standard
-
-**OPSX is now the default workflow for OpenSpec.** It's a fluid, iterative approach that replaces rigid phases with flexible actions you can take anytime.
-
-**Key improvements:**
-- **Schema-driven**: Edit `schema.yaml` and `templates/*.md` to customize workflows without code changes
-- **Fluid actions**: Create, implement, update, archive — do any of them anytime
-- **Hackable**: Experiment with instructions, test granularly, customize workflows
-- **Team-ready**: Create workflows that match how your team actually works
-
-```bash
-# Quick start with OPSX
-openspec init
-# Then in your AI chat:
-/opsx:explore      # Think through ideas
-/opsx:propose      # Create change with planning artifacts
-/opsx:apply        # Implement tasks
-/opsx:archive      # Archive when done
-```
-
-### 🆕 New AI Tool Integrations
-
-- **Atlassian Rovo Dev CLI** support (`--tools rovodev`)
-- **MiniMax Code** as a global skills-only tool target
-- **Enhanced GitHub Copilot** integration with opt-in cloud coding agent files
-- **Improved Codex skills** now use the shared `.agents` directory
-
-### � New Plan Artifact
-
-- **Mandatory planning artifact** with implementation guidance
-- **Code maps** showing files to create, modify, and delete
-- **Implementation order** with sequenced steps
-- **Test plans** covering unit, integration, and manual testing
-- **Risk assessment** with mitigation strategies
-- **Dependency chain**: specs → design → plan → tasks
-
-### 🔧 Enhanced Features
-
-- **OPSX Modify Command** (experimental): `/opsx:modify` for revising planning artifacts before implementation
-- **Dependency propagation**: Automatic updates to dependent artifacts when modifying
-- **Conflict detection**: Identifies conflicts with manual edits before modification
-- **Modification history**: Tracks all artifact changes with timestamps
-
-### �🔧 Enhanced Features
-
-- **Capability retirement**: Automatically retire capabilities when changes remove their last requirements
-- **Multi-language validation**: `openspec validate` now treats English `SHALL`/`MUST` as guidance in normal mode
-- **Better task progress**: Counts indented sub-tasks and provides more accurate progress tracking
-- **Improved archive guidance**: Better error messages and flag suggestions for non-interactive environments
-
-## 📚 How It Works
-
-```
-┌────────────────────┐
-│ Draft Change       │
-│ Proposal           │
-└────────┬───────────┘
-         │ share intent with your AI
-         ▼
-┌────────────────────┐
-│ Review & Align     │
-│ (edit specs/tasks) │◀──── feedback loop ──────┐
-└────────┬───────────┘                          │
-         │ approved plan                        │
-         ▼                                      │
-┌────────────────────┐                          │
-│ Implement Tasks    │──────────────────────────┘
-│ (AI writes code)   │
-└────────┬───────────┘
-         │ ship the change
-         ▼
-┌────────────────────┐
-│ Archive & Update   │
-│ Specs (source)     │
-└────────────────────┘
-
-1. Draft a change proposal that captures the spec updates you want
-2. Review the proposal with your AI assistant until everyone agrees
-3. Implement tasks that reference the agreed specs
-4. Archive the change to merge the approved updates back into the source-of-truth specs
-```
-
-## 🚀 Getting Started
-
-### Prerequisites
-- **Node.js >= 20.19.0** - Check your version with `node --version`
-
-### Step 1: Install the CLI globally
-
-**Option A: Using npm**
-```bash
-npm install -g @codewalla_india/openspec@latest
-```
-
-Verify installation:
-```bash
-openspec --version
-```
-
-**Option B: Using Nix (NixOS and Nix package manager)**
-```bash
-nix run github:codewalla-engineering/openspec-upstream-sync -- init
-```
-
-Or install to your profile:
-```bash
-nix profile install github:codewalla-engineering/openspec-upstream-sync
-```
-
-### Step 2: Initialize OpenSpec in your project
-
-```bash
-cd your-project
-openspec init
-```
-
-This creates:
-- `openspec/` directory for your specs and changes
-- AI tool integration files (slash commands or skills)
-- Optional project configuration (`openspec/config.yaml`)
-
-### Step 3: Start using OpenSpec
-
-**In your AI assistant's chat:**
-
-```bash
-# Explore an idea (recommended first step)
-/opsx:explore
-
-# Create a new change
-/opsx:propose add-dark-mode
-
-# Implement the tasks
-/opsx:apply
-
-# Archive when complete
-/opsx:archive
-```
-
-## 🛠️ Supported AI Tools
-
-OpenSpec integrates with 30+ AI coding assistants. Here are the most popular:
-
-### Native Slash Commands
-These tools have built-in OpenSpec commands:
-
-| Tool | Commands |
-|------|----------|
-| **Claude Code** | `/openspec:proposal`, `/openspec:apply`, `/openspec:archive` |
-| **Cursor** | `/openspec-proposal`, `/openspec-apply`, `/openspec:archive` |
-| **GitHub Copilot** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
-| **Windsurf** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
-| **Continue** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
-| **Cline** | Workflows in `.clinerules/workflows/` directory |
-| **Codex** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` (auto-installed) |
-
-### AGENTS.md Compatible
-These tools automatically read workflow instructions from `openspec/AGENTS.md`:
-
-| Tools |
-|-------|
-| Amp • Jules • Others |
-
-For the complete list of supported tools, see [Supported Tools](docs/supported-tools.md).
-
-## 📖 Documentation
-
-### Start Here
-- [Getting Started](docs/getting-started.md) - Install, initialize, and run your first change
-- [OPSX Workflow](docs/opsx.md) - The new fluid, schema-driven workflow
-- [How Commands Work](docs/how-commands-work.md) - Where to type slash commands vs terminal commands
-
-### Core Concepts
-- [Core Concepts at a Glance](docs/overview.md) - The mental model on one page
-- [Concepts](docs/concepts.md) - In-depth explanation of specs, changes, artifacts
-- [Glossary](docs/glossary.md) - Every term defined in one place
-
-### Day-to-Day Usage
-- [Workflows](docs/workflows.md) - Common patterns and when to reach for each command
-- [Examples & Recipes](docs/examples.md) - Full walkthroughs of real changes
-- [Writing Good Specs](docs/writing-specs.md) - What strong requirements look like
-- [Reviewing Changes](docs/reviewing-changes.md) - The two-minute review pass
-- [Commands Reference](docs/commands.md) - Complete reference for all OPSX commands including `/opsx:modify`
-
-### Advanced
-- [Customization](docs/customization.md) - Project config, custom schemas, shared context
-- [Multi-Language](docs/multi-language.md) - Generate artifacts in other languages
-- [Stores (beta)](docs/stores-beta/user-guide.md) - Plan across repos and teams
-
-### Help
-- [FAQ](docs/faq.md) - Quick answers to common questions
-- [Troubleshooting](docs/troubleshooting.md) - Concrete fixes for concrete failures
-- [Migration Guide](docs/migration-guide.md) - Moving from legacy workflow to OPSX
-
-## 🔄 Migration from Legacy Workflow
-
-If you're using the old OpenSpec workflow, the [Migration Guide](docs/migration-guide.md) explains what changed and how to transition. Your existing work is safe — the migration is non-destructive.
-
-## 🤝 Contributing
-
-We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. The most valuable contributions are:
-
-- Documentation improvements
-- Bug fixes
-- New AI tool integrations
-- Workflow enhancements
-
-## 📄 License
-
-MIT License - see [LICENSE](LICENSE) file for details
-
-## 🆘 Support
-
-- **Discord:** [discord.gg/YctCnvvshC](https://discord.gg/YctCnvvshC) for questions, ideas, and help
-- **GitHub Issues:** [github.com/codewalla-engineering/openspec-upstream-sync/issues](https://github.com/codewalla-engineering/openspec-upstream-sync/issues) for bugs and feature requests
-- **Feedback:** Run `openspec feedback "your message"` to send feedback directly from your terminal
-
-## 🌟 Acknowledgments
-
-Built with ❤️ for the AI-assisted development community. Special thanks to all contributors who make OpenSpec better every day.
-
----
-
+<p align="center">
+  <a href="https://github.com/codewalla-engineering/openspec-upstream-sync">
+    <picture>
+      <source srcset="assets/openspec_pixel_dark.svg" media="(prefers-color-scheme: dark)">
+      <source srcset="assets/openspec_pixel_light.svg" media="(prefers-color-scheme: light)">
+      <img src="assets/openspec_pixel_light.svg" alt="OpenSpec logo" height="64">
+    </picture>
+  </a>
+
+</p>
+<p align="center">Spec-driven development for AI coding assistants.</p>
+<p align="center">
+  <a href="https://github.com/codewalla-engineering/openspec-upstream-sync/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/codewalla-engineering/openspec-upstream-sync/actions/workflows/ci.yml/badge.svg" /></a>
+  <a href="https://www.npmjs.com/package/@codewalla_india/openspec"><img alt="npm version" src="https://img.shields.io/npm/v/@codewalla_india/openspec?style=flat-square" /></a>
+  <a href="https://nodejs.org/"><img alt="node version" src="https://img.shields.io/node/v/@codewalla_india/openspec?style=flat-square" /></a>
+  <a href="./LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" /></a>
+  <a href="https://conventionalcommits.org"><img alt="Conventional Commits" src="https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg?style=flat-square" /></a>
+  <a href="https://discord.gg/YctCnvvshC"><img alt="Discord" src="https://img.shields.io/badge/Discord-Join%20the%20community-5865F2?logo=discord&logoColor=white&style=flat-square" /></a>
+</p>
+
+<p align="center">
+  <img src="assets/codewalla_bg.png" alt="OpenSpec dashboard preview" width="90%">
+</p>
+
+<p align="center">
+  Follow <a href="https://x.com/0xTab">@0xTab on X</a> for updates · Join the <a href="https://discord.gg/YctCnvvshC">OpenSpec Discord</a> for help and questions.
+</p>
+
+<p align="center">
+  <sub>🚀 <strong>New:</strong> <a href="docs/opsx.md">OPSX Workflow</a> — schema-driven, hackable, fluid. Iterate on workflows without code changes.</sub>
+</p>
+
+# OpenSpec
+
+OpenSpec aligns humans and AI coding assistants with spec-driven development so you agree on what to build before any code is written. **No API keys required.**
+
+## 🎯 Why OpenSpec?
+
+AI coding assistants are powerful but unpredictable when requirements live in chat history. OpenSpec adds a lightweight specification workflow that locks intent before implementation, giving you deterministic, reviewable outputs.
+
+Key outcomes:
+- Human and AI stakeholders agree on specs before work begins
+- Structured change folders (proposals, tasks, and spec updates) keep scope explicit and auditable
+- Shared visibility into what's proposed, active, or archived
+- Works with the AI tools you already use: custom slash commands where supported, context rules everywhere else
+
+## 🌟 What's New in v1.8.0
+
+### 🚀 OPSX Workflow - The New Standard
+
+**OPSX is now the default workflow for OpenSpec.** It's a fluid, iterative approach that replaces rigid phases with flexible actions you can take anytime.
+
+**Key improvements:**
+- **Schema-driven**: Edit `schema.yaml` and `templates/*.md` to customize workflows without code changes
+- **Fluid actions**: Create, implement, update, archive — do any of them anytime
+- **Hackable**: Experiment with instructions, test granularly, customize workflows
+- **Team-ready**: Create workflows that match how your team actually works
+
+```bash
+# Quick start with OPSX
+openspec init
+# Then in your AI chat:
+/opsx:explore      # Think through ideas
+/opsx:propose      # Create change with planning artifacts
+/opsx:apply        # Implement tasks
+/opsx:archive      # Archive when done
+```
+
+### 🆕 New AI Tool Integrations
+
+- **Atlassian Rovo Dev CLI** support (`--tools rovodev`)
+- **MiniMax Code** as a global skills-only tool target
+- **Enhanced GitHub Copilot** integration with opt-in cloud coding agent files
+- **Improved Codex skills** now use the shared `.agents` directory
+
+### � New Plan Artifact
+
+- **Mandatory planning artifact** with implementation guidance
+- **Code maps** showing files to create, modify, and delete
+- **Implementation order** with sequenced steps
+- **Test plans** covering unit, integration, and manual testing
+- **Risk assessment** with mitigation strategies
+- **Dependency chain**: specs → design → plan → tasks
+
+### 🔧 Enhanced Features
+
+- **OPSX Modify Command** (experimental): `/opsx:modify` for revising planning artifacts before implementation
+- **Dependency propagation**: Automatic updates to dependent artifacts when modifying
+- **Conflict detection**: Identifies conflicts with manual edits before modification
+- **Modification history**: Tracks all artifact changes with timestamps
+
+### �🔧 Enhanced Features
+
+- **Capability retirement**: Automatically retire capabilities when changes remove their last requirements
+- **Multi-language validation**: `openspec validate` now treats English `SHALL`/`MUST` as guidance in normal mode
+- **Better task progress**: Counts indented sub-tasks and provides more accurate progress tracking
+- **Improved archive guidance**: Better error messages and flag suggestions for non-interactive environments
+
+## 📚 How It Works
+
+```
+┌────────────────────┐
+│ Draft Change       │
+│ Proposal           │
+└────────┬───────────┘
+         │ share intent with your AI
+         ▼
+┌────────────────────┐
+│ Review & Align     │
+│ (edit specs/tasks) │◀──── feedback loop ──────┐
+└────────┬───────────┘                          │
+         │ approved plan                        │
+         ▼                                      │
+┌────────────────────┐                          │
+│ Implement Tasks    │──────────────────────────┘
+│ (AI writes code)   │
+└────────┬───────────┘
+         │ ship the change
+         ▼
+┌────────────────────┐
+│ Archive & Update   │
+│ Specs (source)     │
+└────────────────────┘
+
+1. Draft a change proposal that captures the spec updates you want
+2. Review the proposal with your AI assistant until everyone agrees
+3. Implement tasks that reference the agreed specs
+4. Archive the change to merge the approved updates back into the source-of-truth specs
+```
+
+## 🚀 Getting Started
+
+### Prerequisites
+- **Node.js >= 20.19.0** - Check your version with `node --version`
+
+### Step 1: Install the CLI globally
+
+**Option A: Using npm**
+```bash
+npm install -g @codewalla_india/openspec@latest
+```
+
+Verify installation:
+```bash
+openspec --version
+```
+
+**Option B: Using Nix (NixOS and Nix package manager)**
+```bash
+nix run github:codewalla-engineering/openspec-upstream-sync -- init
+```
+
+Or install to your profile:
+```bash
+nix profile install github:codewalla-engineering/openspec-upstream-sync
+```
+
+### Step 2: Initialize OpenSpec in your project
+
+```bash
+cd your-project
+openspec init
+```
+
+This creates:
+- `openspec/` directory for your specs and changes
+- AI tool integration files (slash commands or skills)
+- Optional project configuration (`openspec/config.yaml`)
+
+### Step 3: Start using OpenSpec
+
+**In your AI assistant's chat:**
+
+```bash
+# Explore an idea (recommended first step)
+/opsx:explore
+
+# Create a new change
+/opsx:propose add-dark-mode
+
+# Implement the tasks
+/opsx:apply
+
+# Archive when complete
+/opsx:archive
+```
+
+## 🛠️ Supported AI Tools
+
+OpenSpec integrates with 30+ AI coding assistants. Here are the most popular:
+
+### Native Slash Commands
+These tools have built-in OpenSpec commands:
+
+| Tool | Commands |
+|------|----------|
+| **Claude Code** | `/openspec:proposal`, `/openspec:apply`, `/openspec:archive` |
+| **Cursor** | `/openspec-proposal`, `/openspec-apply`, `/openspec:archive` |
+| **GitHub Copilot** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
+| **Windsurf** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
+| **Continue** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
+| **Cline** | Workflows in `.clinerules/workflows/` directory |
+| **Codex** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` (auto-installed) |
+
+### AGENTS.md Compatible
+These tools automatically read workflow instructions from `openspec/AGENTS.md`:
+
+| Tools |
+|-------|
+| Amp • Jules • Others |
+
+For the complete list of supported tools, see [Supported Tools](docs/supported-tools.md).
+
+## 📖 Documentation
+
+### Start Here
+- [Getting Started](docs/getting-started.md) - Install, initialize, and run your first change
+- [OPSX Workflow](docs/opsx.md) - The new fluid, schema-driven workflow
+- [How Commands Work](docs/how-commands-work.md) - Where to type slash commands vs terminal commands
+
+### Core Concepts
+- [Core Concepts at a Glance](docs/overview.md) - The mental model on one page
+- [Concepts](docs/concepts.md) - In-depth explanation of specs, changes, artifacts
+- [Glossary](docs/glossary.md) - Every term defined in one place
+
+### Day-to-Day Usage
+- [Workflows](docs/workflows.md) - Common patterns and when to reach for each command
+- [Examples & Recipes](docs/examples.md) - Full walkthroughs of real changes
+- [Writing Good Specs](docs/writing-specs.md) - What strong requirements look like
+- [Reviewing Changes](docs/reviewing-changes.md) - The two-minute review pass
+- [Commands Reference](docs/commands.md) - Complete reference for all OPSX commands including `/opsx:modify`
+
+### Advanced
+- [Customization](docs/customization.md) - Project config, custom schemas, shared context
+- [Multi-Language](docs/multi-language.md) - Generate artifacts in other languages
+- [Stores (beta)](docs/stores-beta/user-guide.md) - Plan across repos and teams
+
+### Help
+- [FAQ](docs/faq.md) - Quick answers to common questions
+- [Troubleshooting](docs/troubleshooting.md) - Concrete fixes for concrete failures
+- [Migration Guide](docs/migration-guide.md) - Moving from legacy workflow to OPSX
+
+## 🔄 Migration from Legacy Workflow
+
+If you're using the old OpenSpec workflow, the [Migration Guide](docs/migration-guide.md) explains what changed and how to transition. Your existing work is safe — the migration is non-destructive.
+
+## 🤝 Contributing
+
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. The most valuable contributions are:
+
+- Documentation improvements
+- Bug fixes
+- New AI tool integrations
+- Workflow enhancements
+
+## 📄 License
+
+MIT License - see [LICENSE](LICENSE) file for details
+
+## 🆘 Support
+
+- **Discord:** [discord.gg/YctCnvvshC](https://discord.gg/YctCnvvshC) for questions, ideas, and help
+- **GitHub Issues:** [github.com/codewalla-engineering/openspec-upstream-sync/issues](https://github.com/codewalla-engineering/openspec-upstream-sync/issues) for bugs and feature requests
+- **Feedback:** Run `openspec feedback "your message"` to send feedback directly from your terminal
+
+## 🌟 Acknowledgments
+
+Built with ❤️ for the AI-assisted development community. Special thanks to all contributors who make OpenSpec better every day.
+
+---
+
 **⚡ Powered by OPSX Workflow — the future of spec-driven development**

package/dist/comprehension-quiz/index.d.ts

@@ -11,15 +11,15 @@
  * @example
  * ```ts
  * import { QuizExecutor } from './comprehension-quiz/quiz-executor.js';
- * import { generateQuizQuestions } from './comprehension-quiz/question-generator.js';
- * import { createProviderWithFallback } from './comprehension-quiz/providers/factory.js';
+ * import { QuizQuestionStream, getQuestionCount } from './comprehension-quiz/question-generator.js';
  *
- * // Generate questions
- * const questions = await generateQuizQuestions(artifactPaths, 10);
+ * // Create on-demand stream — NO questions generated yet
+ * const totalQuestions = getQuestionCount(totalArtifactBytes);
+ * const stream = await QuizQuestionStream.create(artifactPaths, totalQuestions);
  *
- * // Execute quiz
+ * // Execute quiz — one question fetched per answer
  * const executor = new QuizExecutor();
- * const result = await executor.executeQuiz(questions);
+ * const result = await executor.executeQuiz(stream, changeName);
  *
  * if (result.passed) {
  *   console.log('Quiz passed! Proceeding with implementation.');
@@ -38,5 +38,5 @@ export { LocalProvider } from './providers/local.js';
 export { fingerprintFile, fingerprintDirectory, fingerprintArtifacts, isPassRecordValid } from './fingerprint.js';
 export * from './pass-record.js';
 export { QuizExecutor } from './quiz-executor.js';
-export { generateQuizQuestions, generateQuestionsForArtifact, getQuestionCount, calculateQuestionAllocation, } from './question-generator.js';
+export { generateQuizQuestions, generateQuestionsForArtifact, getQuestionCount, calculateQuestionAllocation, QuizQuestionStream, } from './question-generator.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/comprehension-quiz/index.js

@@ -11,15 +11,15 @@
  * @example
  * ```ts
  * import { QuizExecutor } from './comprehension-quiz/quiz-executor.js';
- * import { generateQuizQuestions } from './comprehension-quiz/question-generator.js';
- * import { createProviderWithFallback } from './comprehension-quiz/providers/factory.js';
+ * import { QuizQuestionStream, getQuestionCount } from './comprehension-quiz/question-generator.js';
  *
- * // Generate questions
- * const questions = await generateQuizQuestions(artifactPaths, 10);
+ * // Create on-demand stream — NO questions generated yet
+ * const totalQuestions = getQuestionCount(totalArtifactBytes);
+ * const stream = await QuizQuestionStream.create(artifactPaths, totalQuestions);
  *
- * // Execute quiz
+ * // Execute quiz — one question fetched per answer
  * const executor = new QuizExecutor();
- * const result = await executor.executeQuiz(questions);
+ * const result = await executor.executeQuiz(stream, changeName);
  *
  * if (result.passed) {
  *   console.log('Quiz passed! Proceeding with implementation.');
@@ -43,5 +43,5 @@ export * from './pass-record.js';
 // Quiz execution
 export { QuizExecutor } from './quiz-executor.js';
 // Question generation
-export { generateQuizQuestions, generateQuestionsForArtifact, getQuestionCount, calculateQuestionAllocation, } from './question-generator.js';
+export { generateQuizQuestions, generateQuestionsForArtifact, getQuestionCount, calculateQuestionAllocation, QuizQuestionStream, } from './question-generator.js';
 //# sourceMappingURL=index.js.map

package/dist/comprehension-quiz/providers/anthropic.d.ts

@@ -30,5 +30,6 @@ export declare class AnthropicProvider extends BaseProvider {
      * @returns Array of generated questions
      */
     generateQuestions(artifactContent: string, questionCount: number, artifactType: 'proposal' | 'design' | 'specs' | 'plan' | 'tasks'): Promise<Question[]>;
+    generateSingleQuestion(artifactContent: string, artifactType: 'proposal' | 'design' | 'specs' | 'plan' | 'tasks', questionIndex: number, totalQuestions: number, previousQuestionTexts: string[]): Promise<Question>;
 }
 //# sourceMappingURL=anthropic.d.ts.map