@chongyan/autospec 1.0.2 → 1.0.3

package/README.en.md

@@ -1,598 +0,0 @@
-<div align="center">
-
-# AutoSpec
-
-**Autonomous Software Development Pipeline — AI drives the full cycle, humans stay on the loop.**
-
-[中文文档](./README.md) · [Quick Start](#quick-start) · [Core Principles](#core-principles) · [How It Works](#how-it-works) · [Knowledge Structure](#knowledge-structure) · [Contributing](./CONTRIBUTING.md)
-
-</div>
-
----
-
-## One-Sentence Value
-
-AutoSpec is an AI-driven development pipeline that automates the entire software delivery process — from requirement analysis to deployment. Instead of replacing developers, it structures the AI's work through a rigorous, verifiable pipeline with constitutional safety guards.
-
-**Not "AI writes code faster" — but "AI autonomously completes the full SDLC with human oversight at key decision points."**
-
-## Key Features
-
-| Feature | Description |
-|---------|-------------|
-| **AI Autonomous Development** | Full pipeline from requirements to deployment |
-| **Double-Layer Validation** | Deterministic verification → AI review |
-| **Do-Review Separation** | Different AI instances, information isolation |
-| **Constitutional Safety** | 15 red lines, irreversible actions require human confirmation |
-| **Self-Evolution** | Practical experience feeds back, continuous improvement |
-
----
-
-## Vision & Mission
-
-### Vision
-
-**Make AI a reliable development partner, unleashing human creativity.**
-
-We believe AI should not replace humans, but become humanity's most reliable collaboration partner. By taking on repetitive, deterministic R&D work, AI frees humans from tedious coding tasks, allowing us to focus on high-value work that truly requires creativity and strategic thinking.
-
-### Mission
-
-**Build an autonomous automated product development framework, where AI drives the complete SDLC and humans focus on high-value decisions.**
-
-AutoSpec's mission is to achieve "Human On the Loop" rather than "Human In the Loop" collaboration model:
-- **AI Responsible For**: Requirement analysis, design planning, implementation, code review, testing verification, delivery deployment
-- **Human Responsible For**: Direction decisions, safety confirmation, value judgments, exception handling
-
-### Core Values
-
-| Value | Description |
-|-------|-------------|
-| **Verification First** | Deterministic verification > AI review > AI self-review |
-| **Minimal Viable Process** | One file if possible; 5-minute onboarding |
-| **Progressive Autonomy** | From "human reviews every step" to "human only manages harness" |
-| **Safety First** | 15 constitutional red lines, irreversible actions require human confirmation |
-| **Continuous Evolution** | Three-layer self-evolution system, practical experience automatically feeds back |
-
----
-
-## Quick Start
-
-### 1. Installation
-
-```bash
-# Install globally
-npm install -g @chongyan/autospec
-
-# Verify installation
-autospec --help
-```
-
-**Requirements**: Node.js >= 18.0.0
-
-### 2. Initialize Project
-
-```bash
-cd your-project
-autospec init
-```
-
-**Init Options:**
-
-| Option | Shorthand | Description | Values |
-|--------|-----------|-------------|--------|
-| `--workflow` | `-w` | Iteration mode | `waterfall` (default), `agile`, `experiment`, `hotfix` |
-| `--roles` | `-r` | Roles | `backend`, `frontend`, `data`, `ai`, `quality` |
-| `--domain` | `-d` | Domain (free text) | `fintech payment`, `ecommerce`... |
-
-```bash
-# Default: waterfall + generic domain
-autospec init
-
-# Hotfix workflow + backend role
-autospec init -w hotfix -r backend
-
-# Agile workflow + backend/AI roles
-autospec init -w agile -r backend,ai
-
-# Fintech domain + backend/data roles
-autospec init -d "fintech payment" -r backend,data
-```
-
-### 3. Start Full Pipeline
-
-In Claude Code:
-
-```bash
-/autospec:run
-/autospec:run Build a user favorites feature with category filtering
-```
-
-> **Note**: `/autospec:run` already includes the complete requirement exploration phase (CEO alignment + requirement analysis), no need to run `/autospec:explore` separately.
-
-### Execution Modes
-
-| Mode | Description | Use Case |
-|------|-------------|----------|
-| **Autonomous Mode** | Full pipeline auto-execution, AI makes decisions | Automated development, unattended |
-| **Interactive Mode** | Stage-by-stage execution, human confirmation required | Learning phase, complex projects, safety-critical |
-
-**Recommendation**: Start with interactive mode for first use, switch to autonomous mode after familiarizing with the workflow.
-
----
-
-## Core Principles
-
-### The Triangular Prism: First Principles
-
-```
-        Verification-First
-       /                  \
-      /                    \
-  Minimal-Viable ——— Progressive-Autonomy
-```
-
-#### Verification-First
-
-> "Accelerate the verification loop, not wait for models to improve." — Karpathy
-
-AI outputs are **inherimately non-deterministic**. You cannot trust its "I'm done" — only trust **verifiable evidence**.
-
-AutoSpec establishes a double-layer validation system:
-- **Layer 1 (Deterministic)**: Build, test, lint, type-check — machine judgment, non-negotiable
-- **Layer 2 (AI Review)**: Independent AI instance evaluation with structured evidence
-
-Layer 1 fails → Layer 2 never runs.
-
-#### Minimal-Viable Process
-
-> "Users should understand the structure and start using within 5 minutes." — Design Iron Rule
-
-Minimal doesn't mean cutting corners — it means **not doing unnecessary things**:
-- One file if possible, not two
-- Markdown if possible, not code
-- One workflow doesn't fit all — choose dynamically based on complexity
-- Build high-frequency capabilities in advance, build low-frequency when needed
-
-#### Progressive Autonomy
-
-> "Human On the Loop — don't inspect outputs, engineer the harness." — Kief Morris
-
-Trust is earned, not given by default:
-- **Interactive Mode**: Confirm after each stage before proceeding
-- **Autonomous Mode**: Confirm at requirements, design, delivery; autonomous in between
-
-When unsatisfied with outputs, **change the harness, not the outputs**.
-
-### Core Design Principles
-
-See [`knowledge/01-principles/01-first-principles.md`](knowledge/01-principles/01-first-principles.md) for complete list.
-
-| Principle | One-Liner |
-|-----------|-----------|
-| **DP1** Double-Layer Validation | Deterministic + AI review, Layer 1 must pass before Layer 2 |
-| **DP2** Do-Review Separation | Producer and reviewer are different AI instances with information isolation |
-| **DP6** Precision Retry | Retry only failed items, not full redo |
-| **DP8** CSO Principle | Skill description only writes trigger conditions, forcing full load |
-| **DP10** Safety & Emergency Stop | Four-layer safety + stop-the-line + irreversible guard |
-| **DP16** Template-as-Constraint | Structured templates constrain output, prevention over detection |
-| **DP17** Structured Clarification | 11-dimension scan + max 5 questions + AI recommended answers |
-| **DP18** Cross-Artifact Consistency | 6-dimension check: duplicate/ambiguity/spec-gap/constitution-align/coverage/term-drift |
-
----
-
-## How It Works
-
-### Development Pipeline
-
-```
-[Stage 0]  →  Requirement  →  Design  →  Implementation  →  Review  →  Testing  →  Delivery
- Env Check     Analysis       Planning   (+ quick test)     (isolated)   QA         Deploy
-                  ↓              ↓            ↓                ↓          ↓           ↓
-              [Layer 1]     [Layer 1]    [Layer 1]         [Layer 1]  [Layer 1]   [Layer 1]
-              [Layer 2]     [Layer 2]    [Layer 2]         [Layer 2]  [Layer 2]   [Layer 2]
-```
-
-**Double-Layer Validation**:
-- **Layer 1 (Deterministic)**: Build/test/lint/type-check — machine judgment, non-negotiable
-- **Layer 2 (AI Review)**: Independent AI instance with structured evidence review
-
-Layer 1 fails → Layer 2 never runs.
-
-### CEO Exploration Mechanism
-
-Before requirement analysis, AutoSpec uses dual-agent debate to clarify requirements:
-
-- **ceo**: Explores from CEO/strategy perspective (business value, strategic alignment)
-- **product-owner**: Challenges from product feasibility angle (UX, scope, data-driven decisions)
-
-**Autonomous mode**: Agents debate automatically → consensus becomes requirement, disagreements marked for clarification
-
-**Interactive mode**: AI asks 5 strategic questions with recommended answers → user confirms
-
-### Iteration Modes
-
-| Mode | Stages | Description | Use Case |
-|------|--------|-------------|----------|
-| **Waterfall** | 01→02→03→04→05→06 | Full 6-stage pipeline | New features, major changes |
-| **Agile** | 01 + [02→03→04]×N + 05→06 | Story-driven cycles | Iterative development |
-| **Experiment** | 01→02→03 + Evaluation | Prototype + AI evaluation | Technical exploration |
-| **Hotfix** | 01→03→04→06 | Fast track with basic tests | Emergency fixes |
-
----
-
-## Command System
-
-### Slash Commands (AI-Driven)
-
-#### Autonomous Mode (Recommended)
-
-| Command | Description |
-|---------|-------------|
-| `/autospec:run` | Full pipeline autonomous execution + workflow selection |
-
-**Parameters:**
-| Parameter | Shorthand | Description | Values |
-|-----------|-----------|-------------|--------|
-| `--workflow` | `-w` | Iteration mode | `waterfall`, `agile`, `experiment`, `hotfix` |
-| `--roles` | `-r` | Roles | `backend`, `frontend`, `data`, `ai`, `quality` |
-| `--domain` | `-d` | Domain (free text) | `fintech payment system`... |
-
-#### Interactive Mode (Stage-by-Stage)
-
-| Command | Chinese | Description |
-|---------|---------|-------------|
-| `/autospec:explore` | "我先想想" | Requirement exploration (CEO alignment + analysis) |
-| `/autospec:propose` | "就这么干" | Design planning |
-| `/autospec:apply` | "开工，按单子做" | Implementation (code + review + testing) |
-| `/autospec:archive` | "做完了，收工" | Delivery + evolution archival |
-
-#### Evolution Commands
-
-| Command | Level | Description |
-|---------|-------|-------------|
-| `/self-evolve` | L1 Framework | AutoSpec framework's own iteration and upgrade |
-| `/autospec:field-evolve` | L2 Domain | Learn and extract capabilities from实战 projects |
-| `/autospec:project-evolve` | L3 Project | Project's own code, config, documentation optimization |
-
-#### Utility Commands
-
-| Command | Description |
-|---------|-------------|
-| `/autospec:status` | View pipeline progress |
-| `/autospec:test` | Unified test command (validate + fix + evaluate) |
-| `/autospec:memory` | Manage project memory system |
-
-### CLI Commands
-
-```bash
-# Initialize
-autospec init                              # Default: waterfall + generic domain
-autospec init -w hotfix -r backend         # Hotfix workflow + backend role
-autospec init -w agile -r backend,ai       # Agile workflow + backend/AI roles
-autospec init -d "fintech payment" -r backend,data  # Fintech domain + backend/data roles
-
-# Status and update
-autospec list                              # List all slash commands
-autospec update                            # Update framework (preserve state)
-```
-
-### Environment Integration Commands
-
-`autospec init` automatically detects middleware and components in your project. Environment knowledge management commands:
-
-```bash
-/autospec:env                      # View environment configuration
-/autospec:env-sync                 # Sync from code + auto-activate
-/autospec:env-validate             # Validate configuration completeness
-/autospec:env-export <dir>         # Export project knowledge base
-/autospec:component                # List available components
-```
-
-**Auto-detection**: `autospec init` automatically scans code for MySQL, Redis, Kafka, MongoDB, Elasticsearch, RabbitMQ, PostgreSQL usage, generates knowledge configs and activates them. See [Environment Integration Protocol](knowledge/06-environment/README.md) for details.
-
----
-
-## Self-Evolution
-
-AutoSpec improves itself through a **three-layer self-evolution system**, forming a complete closed loop from project practice to framework upgrade.
-
-### Three-Layer Evolution System
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  L1: Self-Evolve (Framework Level)                               │
-│  /self-evolve                                                    │
-│  Goal: AutoSpec framework's own iteration and upgrade            │
-│  Output: Framework skills, methodologies, design principles      │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓ Extract
-┌─────────────────────────────────────────────────────────────────┐
-│  L2: Field-Evolve (Domain Level)                                 │
-│  /autospec:field-evolve                                          │
-│  Goal: Framework learns and extracts capabilities from projects  │
-│  Output: Domain skills, best practices, benchmarks               │
-└─────────────────────────────────────────────────────────────────┘
-                              ↓ Apply
-┌─────────────────────────────────────────────────────────────────┐
-│  L3: Project-Evolve (Project Level)                              │
-│  /autospec:project-evolve                                        │
-│  Goal:实战 project's own code, config, documentation optimization│
-│  Output: Code quality improvement, test completion, docs         │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Evolution Zones
-
-| Zone | Level | Contents | Rules |
-|------|-------|----------|-------|
-| **Frozen** | L1 Core | Constitution, evolution rules, core principles | Human-only changes, never auto-modified |
-| **Controlled** | L1/L2 Boundary | Stage definitions, universal skills, role profiles | Auto-proposed, human-approved |
-| **Free** | L2 Domain | Business skills, benchmarks, decision trees | Auto-evolved, validator-verified |
-| **Environment Knowledge** | L3 Project | Environment configs, component libraries, best practices | Project-level auto-optimization |
-
-**Core Safety Principle**: The evolution system cannot modify its own evaluation criteria (immutable harness).
-
-### Enterprise Adaptation
-
-```
-┌─────────────────────────────────┐
-│     Enterprise Overlay          │  ← Org-specific (not upstreamed)
-│  org-constitution.md            │
-│  org-skills/ + domain-knowledge │
-├─────────────────────────────────┤
-│     AutoSpec Core Framework     │  ← npm install (upgradeable)
-│  constitution.md                │
-│  process/ guides/ agents/ ...   │
-└─────────────────────────────────┘
-```
-
-Configure domain overlay via `autospec init --domain <domain>`. The overlay adds domain-specific rules and skills **without forking** the core framework.
-
----
-
-## Safety & Quality
-
-### Five-Layer Safety Protection
-
-1. **Constitutional Gate** — 15 inviolable red lines
-2. **Permission Control** — Each agent only uses its authorized tools
-3. **Stop-the-Line** — Security vulnerability / data loss / 3 failed retries → immediate halt
-   - **Precision Retry**: Level 1 (inline retry) → Level 2 (fix loop, max 3 times) → Level 3 (escalate to human)
-4. **Irreversible Guard** — DB migrations, deployments, external APIs → require human confirmation
-5. **Immutable Harness** — Evolution system cannot modify its own evaluation criteria and constitution
-
-### Quality Monitoring
-
-AutoSpec automatically collects pipeline quality metrics via deterministic hooks:
-
-| Metric | Collection | Purpose |
-|--------|------------|---------|
-| Layer 1 pass rate | `layer1-validator` | Code quality baseline |
-| Retry count | `layer1-validator` | Process smoothness |
-| Human intervention count | `layer1-validator` | Autonomy capability |
-| Scope deviation events | `scope-sentinel` | Implementation discipline |
-| Error patterns | `layer1-validator` | Evolution priority |
-
-Metrics stored in `.autospec/runtime/metrics.json`, automatically merged into practice-log at delivery.
-
----
-
-## Knowledge Structure
-
-AutoSpec's knowledge layer is divided into 9 modules by priority, each independently maintained with detailed README navigation files in the `knowledge/` directory.
-
-### Overview
-
-| No. | Module | Evolution Zone | Description |
-|-----|--------|----------------|-------------|
-| **01** | [principles/](knowledge/01-principles/README.md) | 🔴 Frozen | Principles — Constitution, evolution rules, core principles, design philosophy (4-layer system L1-L4) |
-| **02** | [process/](knowledge/02-process/README.md) | 🟡 Controlled | Process — 6-stage execution flow + 4 workflows (waterfall/agile/experiment/hotfix) |
-| **03** | [guides/](knowledge/03-guides/README.md) | 🟡/🟢 Mixed | Capability guides — 51 skill files (stage execution + review + testing + evolution + AI specialization) |
-| **04** | [checklists/](knowledge/04-checklists/README.md) | 🟡 Controlled | Checklists — Stage-specific checklists (requirement/design/code/test/release) |
-| **05** | [config/](knowledge/05-config/README.md) | 🟡 Controlled | Configuration — Validation patterns, team triggers, role configs (with dynamic decision tree) |
-| **06** | [environment/](knowledge/06-environment/README.md) | 🔵 Environment | Environment knowledge — Middleware, components, integration protocols (auto-detection + knowledge feedback) |
-| **07** | [standards/](knowledge/07-standards/README.md) | 🟡 Controlled | Standards — Coding/review/data consistency/document versioning/risk detection |
-| **08** | [organization/](knowledge/08-organization/README.md) | 🟢 Free | Organization — Vision/Mission, AI Native culture, team metrics, governance committee |
-| **09** | [templates/](knowledge/09-templates/README.md) | 🟡 Controlled | Templates — Standardized document templates (architecture/API/database/product/test/evaluation) |
-
-### 01-principles/ — Principles Layer (Constitutional Level)
-
-> See: [knowledge/01-principles/README.md](knowledge/01-principles/README.md)
-
-The principles layer is AutoSpec's highest guiding principles, containing 4 levels (L1→L2→L3→L4):
-
-| File | Description |
-|------|-------------|
-| [00-principles-hierarchy.md](knowledge/01-principles/00-principles-hierarchy.md) | Principles hierarchy (L1 First Principles→L2 Strategic→L3 Tactical→L4 Operational complete traceability) |
-| [01-first-principles.md](knowledge/01-principles/01-first-principles.md) | L1 First Principles (Triangular Prism: Verification-First, Minimal-Viable, Progressive-Autonomy) |
-| [02-strategic-principles.md](knowledge/01-principles/02-strategic-principles.md) | L2 Strategic Principles (S1 Double-Layer Validation, S2 Do-Review Separation, S3 Harness Engineering, S4 Informed Guessing) |
-| [03-tactical-principles.md](knowledge/01-principles/03-tactical-principles.md) | L3 Tactical Principles (T1-T6: Task Decomposition, Context Management, Precision Retry, etc.) |
-| [04-operational-principles.md](knowledge/01-principles/04-operational-principles.md) | L4 Operational Principles (O1-O4: Coding standard level) |
-| [09-constitution.md](knowledge/01-principles/09-constitution.md) | Project Constitution (15 Red Lines: Safety/Process/Decision/Data/Operations) |
-| [10-evolution-mechanism.md](knowledge/01-principles/10-evolution-mechanism.md) | Self-Evolution Mechanism (Three-Layer Evolution System + Evolution Zones + Auto-Fix) |
-
-### 02-process/ — Process Layer
-
-> See: [knowledge/02-process/README.md](knowledge/02-process/README.md)
-
-The process layer defines AutoSpec's 6-stage execution flow and 4 workflows:
-
-| File | Description |
-|------|-------------|
-| [00-overview.md](knowledge/02-process/00-overview.md) | Process overview, startup gate, execution modes |
-| [01-requirement.md](knowledge/02-process/01-requirement.md) | Requirement Analysis Stage |
-| [02-design.md](knowledge/02-process/02-design.md) | Design Planning Stage |
-| [03-implementation.md](knowledge/02-process/03-implementation.md) | Implementation Stage |
-| [04-review.md](knowledge/02-process/04-review.md) | Code Review Stage |
-| [05-testing.md](knowledge/02-process/05-testing.md) | QA Testing Stage |
-| [06-delivery.md](knowledge/02-process/06-delivery.md) | Delivery Stage |
-
-### 03-guides/ — Capability Guides
-
-> See: [knowledge/03-guides/README.md](knowledge/03-guides/README.md)
-
-Capability guides contain 51 skill files, covering core protocols, stage execution, review skills, testing execution, evolution support, AI specializations:
-
-| Category | No. Range | Files |
-|----------|-----------|-------|
-| Core Protocols | 00-01 | 2 |
-| Stage Execution | 02-08 | 7 |
-| Review Skills | 09-14 | 6 |
-| Testing Execution | 15-17 | 3 |
-| Evolution Support | 18-22 | 5 |
-| Context/Environment | 23-29 | 7 |
-| AI Specializations | 30-41 | 12 |
-| Domain Methodologies | 50-57 | 8 |
-
-### 04-checklists/ — Checklists
-
-> See: [knowledge/04-checklists/README.md](knowledge/04-checklists/README.md)
-
-Checklists for each stage, ensuring quality shift-left:
-
-| File | Description |
-|------|-------------|
-| [00-requirement.md](knowledge/04-checklists/00-requirement.md) | Requirement Checklist |
-| [01-design.md](knowledge/04-checklists/01-design.md) | Design Checklist |
-| [02-code.md](knowledge/04-checklists/02-code.md) | Code Checklist |
-| [03-test.md](knowledge/04-checklists/03-test.md) | Testing Checklist |
-| [04-release.md](knowledge/04-checklists/04-release.md) | Release Checklist |
-
-### 05-config/ — Configuration Files
-
-> See: [knowledge/05-config/README.md](knowledge/05-config/README.md)
-
-Validation patterns, team triggers, role configurations:
-
-| File | Description |
-|------|-------------|
-| [00-validation-patterns.yaml](knowledge/05-config/00-validation-patterns.yaml) | Validation Patterns Configuration |
-| [01-team-stage.yaml](knowledge/05-config/01-team-stage.yaml) | Team Stage Configuration (with triggers) |
-| [02-team-tasks.yaml](knowledge/05-config/02-team-tasks.yaml) | Team Tasks Configuration |
-| [03-role-composition.yaml](knowledge/05-config/03-role-composition.yaml) | Role Composition Configuration (with decision tree) |
-
-### 06-environment/ — Environment Knowledge
-
-> See: [knowledge/06-environment/README.md](knowledge/06-environment/README.md)
-
-Environment integration protocol, enabling AutoSpec to seamlessly integrate with different organizations' middleware, components, custom frameworks:
-
-| File | Description |
-|------|-------------|
-| [00-template-registry.md](knowledge/06-environment/00-template-registry.md) | Template Registry |
-| [01-detection-patterns.yaml](knowledge/06-environment/01-detection-patterns.yaml) | Detection Patterns Configuration |
-
-Template Resources (integrated into 09-templates):
-
-| File | Description |
-|------|-------------|
-| [13-middleware-knowledge.md](knowledge/09-templates/13-middleware-knowledge.md) | Middleware Knowledge Template |
-| [10-component-knowledge.md](knowledge/09-templates/10-component-knowledge.md) | Component Knowledge Template |
-
-### 07-standards/ — Standards
-
-> See: [knowledge/07-standards/README.md](knowledge/07-standards/README.md)
-
-Coding, review, data consistency standards:
-
-| File | Description |
-|------|-------------|
-| [00-coding-style.md](knowledge/07-standards/00-coding-style.md) | Coding Style Guide |
-| [01-code-review.md](knowledge/07-standards/01-code-review.md) | Code Review Standard |
-| [02-data-consistency.md](knowledge/07-standards/02-data-consistency.md) | Data Consistency Standard |
-| [03-document-versioning.md](knowledge/07-standards/03-document-versioning.md) | Document Versioning Standard |
-| [04-risk-detection.md](knowledge/07-standards/04-risk-detection.md) | Risk Detection Standard |
-
-### 08-organization/ — Organization Knowledge
-
-> See: [knowledge/08-organization/README.md](knowledge/08-organization/README.md)
-
-AI Native team culture, vision, governance:
-
-| File | Description |
-|------|-------------|
-| [00-vision-mission.md](knowledge/08-organization/00-vision-mission.md) | Vision, Mission, Core Values (Verification-First, Minimal-Viable, Progressive-Autonomy, Safety-First, Continuous-Evolution) |
-| [01-ai-native-culture.md](knowledge/08-organization/01-ai-native-culture.md) | AI Native Team Culture Handbook (Four Principles, Work Modes, Role Transition) |
-| [02-team-metrics.md](knowledge/08-organization/02-team-metrics.md) | Team Metrics System (AI Capability, Process Efficiency, Quality, Team Health) |
-| [03-committee-structure.md](knowledge/08-organization/03-committee-structure.md) | Governance Committee Structure (Technical/Quality/Strategy Committees + Governance Agents) |
-| [04-governance-metrics.md](knowledge/08-organization/04-governance-metrics.md) | Governance Metrics (DORA/Layer1/Layer2/Benchmarks Pass Rate) |
-| [05-improvement-process.md](knowledge/08-organization/05-improvement-process.md) | Improvement Process (Improvement Sources/Process/Classification/Integration with Self-Evolution) |
-
-### 09-templates/ — Document Templates
-
-> See: [knowledge/09-templates/README.md](knowledge/09-templates/README.md)
-
-Standardized document template library (sorted by priority):
-
-| File | Description |
-|------|-------------|
-| [01-architecture-design.md](knowledge/09-templates/01-architecture-design.md) | Architecture Design Template |
-| [02-api-design.md](knowledge/09-templates/02-api-design.md) | API Design Template |
-| [03-database-design.md](knowledge/09-templates/03-database-design.md) | Database Design Template |
-| [04-product-design.md](knowledge/09-templates/04-product-design.md) | Product Design Template |
-| [05-business-glossary.md](knowledge/09-templates/05-business-glossary.md) | Business Glossary Template |
-| [06-business-rules.md](knowledge/09-templates/06-business-rules.md) | Business Rules Template |
-| [07-business-flows.md](knowledge/09-templates/07-business-flows.md) | Business Flows Template |
-| [08-test-design.md](knowledge/09-templates/08-test-design.md) | Test Design Template |
-| [09-evaluation-design.md](knowledge/09-templates/09-evaluation-design.md) | Evaluation Design (AI/Model) |
-| [10-component-knowledge.md](knowledge/09-templates/10-component-knowledge.md) | Component Knowledge Template |
-| [11-best-practices.md](knowledge/09-templates/11-best-practices.md) | Best Practices Template |
-| [12-domain-model.md](knowledge/09-templates/12-domain-model.md) | Domain Model Template |
-
----
-
-## Plugins Structure
-
-```
-plugins/               # Plugins layer (commands, agents, skills, hooks)
-├── commands/           # Slash command templates
-├── agents/             # Agent definitions (roles + support)
-│   ├── roles/          # Startup team roles (CEO, Product Owner, Engineer, etc.)
-│   └── support/        # Support agents (reviewers, evaluators, stage-gate, etc.)
-├── skills/             # Skill triggers
-│   ├── *-stage/        # Stage skills (requirement/design/implementation/testing/delivery)
-│   ├── *-iteration/    # Iteration skills (waterfall/agile/experiment/hotfix)
-│   ├── field-evolve-*/ # Field evolution skills (scanner/executor/analyzer/fixer/verifier/learner/distiller)
-│   ├── project-evolve-*/ # Project evolution skills (scanner/generator/analyzer/fixer/reviewer/verifier/learner)
-│   └── benchmark-*/    # Benchmark-related skills
-└── hooks/              # Lifecycle hooks (frozen-zone-guard/scope-sentinel/layer1-validator/execution-tracker/environment-manager)
-```
-
-### Latest Skills
-
-**Field Evolution Skills (L2 Field-Evolve)**:
-- `field-evolve-scanner` - Scan practice logs, identify patterns
-- `field-evolve-executor` - Execute evolution workflow
-- `field-evolve-analyzer` - Analyze evolution effectiveness
-- `field-evolve-fixer` - Fix evolution issues
-- `field-evolve-verifier` - Verify evolution results
-- `field-evolve-learner` - Learn from evolution experience
-- `field-evolve-distiller` - Distill universal skills
-
-**Project Evolution Skills (L3 Project-Evolve)**:
-- `project-evolve-scanner` - Scan project code quality
-- `project-evolve-generator` - Generate optimization plans
-- `project-evolve-analyzer` - Analyze project issues
-- `project-evolve-fixer` - Fix project issues
-- `project-evolve-reviewer` - Review fix results
-- `project-evolve-verifier` - Verify fix effectiveness
-- `project-evolve-learner` - Learn from project experience
-
----
-
-## Contributing
-
-We welcome contributions to:
-- Framework pipeline and skill definition improvements
-- Role profiles for new domains
-- CLI tooling enhancements
-- Practice log entries from real usage
-- Enterprise adaptation experience
-- Documentation and translations
-
-See [CONTRIBUTING.md](./CONTRIBUTING.md) for details.
-
-## License
-
-[MIT](./LICENSE)

package/bin/autospec.js

@@ -1,3 +0,0 @@
-#!/usr/bin/env node
-
-import '../scripts/cli/index.js';