adspecs 0.1.12

package/.adspecs/workflows/adspecs/workflow.yml

@@ -0,0 +1,82 @@
+schema_version: "1.0"
+workflow:
+  id: "adspecs"
+  name: "Full SDD Cycle"
+  version: "1.0.1"
+  author: "GitHub"
+  description: "Runs adspecs → plan → tasks → implement with review gates"
+
+requires:
+  # 0.8.5 is the first release with engine-side resolution of the
+  # ``integration: "auto"`` default. Older versions would treat "auto"
+  # as a literal integration key and fail at dispatch.
+  adspecs_version: ">=1.0.1"
+  integrations:
+    # The four commands below (adspecs, plan, tasks, implement) are core
+    # adspecs commands provided by every integration. The list here is an
+    # advisory, non-exhaustive compatibility hint following the documented
+    # ``any: [...]`` schema -- it is NOT a closed set. The workflow runs
+    # against any integration the project was initialized with, including
+    # ones not listed below, as long as that integration provides the four
+    # core commands referenced in ``steps``.
+    any:
+      - "claude"
+      - "copilot"
+      - "gemini"
+      - "opencode"
+
+inputs:
+  spec:
+    type: string
+    required: true
+    prompt: "Describe what you want to build"
+  integration:
+    type: string
+    default: "auto"
+    prompt: "Integration to use (e.g. claude, copilot, gemini; 'auto' uses the project's initialized integration)"
+  scope:
+    type: string
+    default: "full"
+    enum: ["full", "backend-only", "frontend-only"]
+
+steps:
+  - id: biz-analysis
+    command: adspecs.biz-analysis
+    integration: "{{ inputs.integration }}"
+    input:
+      args: "{{ inputs.spec }}"
+  - id: prd
+    command: adspecs.prd
+    integration: "{{ inputs.integration }}"
+    input:
+      args: "{{ inputs.spec }}"
+
+  - id: review-spec
+    type: gate
+    message: "Review the generated spec before planning."
+    options: [approve, reject]
+    on_reject: abort
+
+  - id: plan
+    command: adspecs.plan
+    integration: "{{ inputs.integration }}"
+    input:
+      args: "{{ inputs.spec }}"
+
+  - id: review-plan
+    type: gate
+    message: "Review the plan before generating tasks."
+    options: [approve, reject]
+    on_reject: abort
+
+  - id: tasks
+    command: adspecs.tasks
+    integration: "{{ inputs.integration }}"
+    input:
+      args: "{{ inputs.spec }}"
+
+  - id: implement
+    command: adspecs.implement
+    integration: "{{ inputs.integration }}"
+    input:
+      args: "{{ inputs.spec }}"

package/.adspecs/workflows/workflow-registry.json

@@ -0,0 +1,13 @@
+{
+  "schema_version": "1.0",
+  "workflows": {
+    "speckit": {
+      "name": "Full SDD Cycle",
+      "version": "1.0.0",
+      "description": "Runs prd \u2192 plan \u2192 tasks \u2192 implement with review gates",
+      "source": "bundled",
+      "installed_at": "2026-05-30T02:44:33.908925+00:00",
+      "updated_at": "2026-05-30T02:44:33.908940+00:00"
+    }
+  }
+}

package/.claude-plugin/marketplace.json

@@ -0,0 +1,23 @@
+{
+  "name": "adspecs-marketplace",
+  "owner": {
+    "name": "Qingwen Chen",
+    "email": "cqinwn@qq.com",
+    "url": "https://gitee.com/yuebon/adspecs",
+    "github": "https://gitee.com/yuebon/adspecs"
+  },
+  "plugins": [
+    {
+      "name": "adspecs",
+      "description": "AI Coding研发协同开发插件",
+      "version": "0.1.12",
+      "source": "./",
+      "author": {
+        "name": "Qingwen Chen",
+        "email": "cqinwn@qq.com",
+        "url": "https://gitee.com/yuebon/adspecs",
+        "github": "https://gitee.com/yuebon/adspecs"
+      }
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,14 @@
+{
+  "name": "adspecs",
+  "displayName": "adspecs AI Plugin",
+  "description": "AI first工程规范驱动开发插件",
+  "version": "0.1.12",
+  "author": {
+    "name": "Qingwen Chen",
+    "email": "cqinwn@qq.com",
+    "url": "https://gitee.com/yuebon/adspecs"
+  },
+  "skills": "./skills/",
+  "license": "apache-2.0",
+  "keywords": ["adspecs", "ai", "development"]
+}

package/.qoder-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "adspecs",
+  "displayName": "adspecs AI 工程规范驱动开发插件",
+  "version": "0.1.12",
+  "description": "AI-first specification-driven development plugin for ECP platform full-lifecycle development",
+  "descriptionZh": "AI优先的工程规范驱动开发插件，覆盖需求分析、PRD、系统设计、任务拆解、TDD、代码评审、Wiki同步全流程",
+  "author": {
+    "name": "Qingwen Chen",
+    "email": "cqinwn@qq.com"
+  },
+  "homepage": "https://gitee.com/yuebon/adspecs",
+  "repository": "https://gitee.com/yuebon/adspecs",
+  "logo": "./assets/avatar.svg",
+  "keywords": ["qoder-plugin", "adspecs", "spec-driven", "tdd"],
+  "category": "developer-tools",
+  "tags": ["skill", "specification", "tdd", "documentation"],
+  "skills": "./skills/",
+  "rules": "./rules/",
+  "hooks": "./hooks/hooks.json",
+  "preserveUpstreamMetadata": true
+}

package/CHANGELOG.md

@@ -0,0 +1 @@
+# 版本历史

package/CLAUDE.md

@@ -0,0 +1,207 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+**adspecs AI Plugin** — a Claude Code plugin for ECP (Enterprise Cloud Platform) full-lifecycle AI-driven development. Provides 19 skills (slash commands) covering requirements, SOW authoring, system design, task breakdown, unit testing, code review, feature status tracking, and wiki sync.
+
+- **Plugin name**: `adspecs` (see `.claude-plugin/plugin.json`)
+- **Author**: Qingwen Chen
+- **License**: Apache 2.0
+- **Language**: Chinese (all documentation, templates, and skill instructions are in Chinese)
+- **Runtime**: Node.js (for hook scripts only); no build system needed
+
+## Project Structure
+
+```
+adspecs/
+├── .claude-plugin/              # Plugin metadata (plugin.json, marketplace.json)
+├── .adspecs/                    # Plugin runtime config, templates, scripts & extensions (copied to target projects)
+│   ├── templates/               #   21 standard document templates (PRD, system design, etc.)
+│   ├── extensions/              #   Extension configs (git hooks, etc.)
+│   ├── scripts/                 #   Helper scripts (bash, PowerShell, Python)
+│   ├── feature.json             #   Default feature tracking template (JSON, primary)
+│   ├── feature.yml              #   Feature tracking human-readable view (YAML, synced from JSON)
+│   └── project.json             #   Default project metadata template
+├── skills/                      # 19 skill definitions (each with SKILL.md)
+│   ├── project-init/            #   Project scaffolding
+│   ├── adspecs-biz-analysis/    #   7-step business requirement analysis
+│   ├── adspecs-new-requirement/ #   Deep business requirement analysis + mock review
+│   ├── adspecs-write-sow/       #   Generate Statement of Work (SOW) from project info
+│   ├── adspecs-prd/               #   Generate PRD from natural language
+│   ├── adspecs-clarify/         #   Clarify ambiguities in PRD (≤5 per round)
+│   ├── adspecs-requirement-research/  # Requirements traceability
+│   ├── adspecs-planning/        #   3-step platform architecture planning (scenarios→dependencies→data model)
+│   ├── adspecs-plan/            #   Backend system design (OOA+OOD) + DDL SQL
+│   ├── adspecs-front-spec/      #   Frontend design spec (UI/interaction)
+│   ├── adspecs-tasks/           #   Backend TDD task list
+│   ├── adspecs-front-tasks/     #   Frontend TDD task list
+│   ├── adspecs-analyze/         #   Cross-document consistency analysis (13 dimensions)
+│   ├── adspecs-adversarial-review/  # Multi-role adversarial document review (5 red team roles)
+│   ├── adspecs-git-commit/      #   Auto-commit after spec phases
+│   ├── adspecs-utest/           #   JUnit 5 + Mockito unit test code + reports
+│   ├── adspecs-export-word/     #   Export Markdown to Word (.docx) with cover page + TOC
+│   ├── adspecs-update-status/   #   Feature status update + tracking matrix output
+│   ├── sie-front-code-review/   #   React+TS+AntDesign code review
+│   └── wiki-update/             #   Sync docs/ to wiki/ (full + incremental modes)
+├── references/                  # Reference projects & conventions copied during `/project-init`
+│   ├── docs/40-project_conventions/  #   ECP coding standards (backend + frontend integration)
+│   ├── front-demo/              #   Vue 3 demo project (Vite + TS + Element Plus)
+│   ├── antd-front-demo/         #   Ant Design React demo project
+│   ├── web-ui/                  #   ECP management console shell project
+│   ├── python/                  #   Python reference resources
+│   └── yudaocloud-end-integration/  #   Yudao Cloud backend integration reference
+├── hooks/                       # Node.js hook scripts + hooks.json config
+├── commands/                    # Reserved (empty)
+├── scripts/                     # Reserved (empty)
+└── settings.json                # Plugin-level settings (currently empty)
+```
+
+## Skill System
+
+Each skill lives in `skills/{name}/SKILL.md` with YAML frontmatter (`name`, `description`, `argument-hint`, `compatibility`, `user-invocable`, `disable-model-invocation`). Skills receive user input via `$ARGUMENTS` placeholder and are invoked as slash commands (e.g., `/project-init`, `/adspecs-prd`).
+
+### Skill Pipeline (Recommended Order)
+
+```
+/project-init                    → Scaffold project structure
+/adspecs-planning                → Platform-level architecture planning (3 steps: scenarios→dependencies→data model)
+/adspecs-new-requirement         → Deep business requirement analysis + mock review
+/adspecs-biz-blueprint           → Business blueprint (F1~F6 file system) from requirement analysis
+/adspecs-prd                     → Generate PRD based on business blueprint
+/adspecs-clarify                 → Clarify ambiguities (iterate 2-3 rounds)
+/adspecs-biz-analysis            → Business requirement analysis (alternative entry point)
+/adspecs-write-sow               → Author Statement of Work (SOW) from project/contract info
+/adspecs-requirement-research    → Record requirement sources
+/adspecs-plan                    → Backend system design + DDL SQL
+/adspecs-front-spec              → Frontend design (UI/interaction)
+/adspecs-tasks                   → Backend TDD task list
+/adspecs-front-tasks             → Frontend TDD task list
+/adspecs-analyze                 → Cross-document consistency check
+/adspecs-adversarial-review      → Adversarial multi-role review
+[coding via superpowers]          → Implementation (TDD, subagent-driven)
+/adspecs-utest                   → Generate unit tests + reports
+/adspecs-update-status           → Update feature.json stage status + tracking matrix (drafting→reviewing→approved)
+/sie-front-code-review           → Frontend-specific code review
+/adspecs-export-word             → Export Markdown docs to Word (.docx) with cover page + TOC
+/wiki-update                     → Sync docs to wiki
+```
+
+### Extension Hooks
+
+Skills check for `.adspecs/extensions.yml` in the target project root, supporting `before_*` / `after_*` hooks with `enabled`, `optional`, and `condition` fields. Condition evaluation is delegated to a HookExecutor (not implemented in this plugin).
+
+## Hooks System
+
+Hooks are configured in `hooks/hooks.json` and run as Node.js scripts:
+
+| Event                                             | Script                    | Purpose                                                                                   |
+| ------------------------------------------------- | ------------------------- | ----------------------------------------------------------------------------------------- |
+| `SessionStart`                                    | `session-start.js`        | Injects `skills/using-saeplugin/SKILL.md` as agent context (no-op if skill doesn't exist) |
+| `SessionStart`                                    | `wiki-queue.js init`      | Initialize wiki update queue file in `.claude/`                                           |
+| `SessionStart`                                    | `commit-queue.js init`    | Initialize commit candidates queue file in `.claude/`                                     |
+| `PostToolUse` (Write/Edit on code/doc files)      | `wiki-queue.js enqueue`   | Track changed files for wiki sync                                                         |
+| `PostToolUse` (Write on `pipeline-manifest.json`) | `commit-queue.js enqueue` | Track completed features for commit                                                       |
+| `Stop`                                            | `wiki-queue.js report`    | Suggest wiki sync at session end                                                          |
+| `Stop`                                            | `commit-queue.js report`  | Suggest commit at session end                                                             |
+
+Hook scripts use `__dirname` for path resolution (not CWD). Queue files stored in `.claude/` (`.commit-candidates`, `.wiki-update-queue`).
+
+## Path Configuration
+
+Skills support configurable output directories via `.adspecs/paths.json` in the target project root. Each skill reads this file at runtime and falls back to hardcoded defaults if the file or specific keys are missing.
+
+### Default Configuration
+
+```json
+{
+  "$schema": "adspecs plugin path configuration",
+  "version": 1,
+  "paths": {
+    "biz_analysis_dir": "docs/00-customer-requirements",
+    "architecture_dir": "docs/10-architecture",
+    "research_output_dir": "docs/02-prd",
+    "sow_dir": "docs/05-sow",
+    "prd_dir": "docs/20-prd",
+    "design_dir": "docs/30-system-design",
+    "test_report_dir": "docs/80-development",
+    "export_dir": "docs/90-export",
+    "wiki_dir": "wiki"
+  }
+}
+```
+
+### Config Keys
+
+| Key                   | Default                         | Used By                                                                                                                             |
+| --------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `biz_analysis_dir`    | `docs/00-customer-requirements` | adspecs-new-requirement                                                                                                             |
+| `architecture_dir`    | `docs/10-architecture`          | adspecs-planning (output), adspecs-new-requirement (input: 识别二级模块)                                                            |
+| `research_output_dir` | `docs/02-prd`                   | adspecs-requirement-research                                                                                                        |
+| `sow_dir`             | `docs/05-sow`                   | adspecs-write-sow                                                                                                                   |
+| `prd_dir`             | `docs/20-prd`                   | adspecs-prd, adspecs-plan (input), adspecs-front-spec (input), wiki-update (source)                                                 |
+| `design_dir`          | `docs/30-system-design`         | adspecs-plan (output), adspecs-tasks, adspecs-front-spec (output), adspecs-front-tasks, adspecs-utest (input), wiki-update (source) |
+| `test_report_dir`     | `docs/80-development`           | adspecs-utest (test reports)                                                                                                        |
+| `export_dir`          | `docs/90-export`                | adspecs-export-word (Word 导出输出)                                                                                                  |
+| `wiki_dir`            | `wiki`                          | wiki-update (output target)                                                                                                         |
+
+`/project-init` generates this file automatically with default values. Users can edit it to customize output paths for their project structure.
+
+## Reference Projects
+
+`references/` (at the plugin root) contains resources copied during `/project-init`:
+
+- **`docs/40-project_conventions/`** — ECP coding standards (backend Java + frontend integration)
+- **`front-demo/`** — Vue 3 demo project (Vite + TypeScript + Element Plus) with `.claude/rules/` for `@gushen` component conventions
+- **`antd-front-demo/`** — Ant Design React demo project
+- **`web-ui/`** — ECP management console shell project
+
+Additionally, `.adspecs/` at the plugin root contains:
+
+- **`templates/`** — 21 standard document templates (PRD, system design, task lists, test reports, security checklist, architecture docs, business proposal, etc.)
+- **`extensions/`** — Extension configurations and scripts
+- **`scripts/`** — Helper scripts (bash, PowerShell, Python)
+- **`feature.json`** / **`project.json`** — Default project metadata templates
+
+## Key Architecture Patterns
+
+### ECP Platform Conventions (Backend)
+
+Backend code generated by this plugin follows strict ECP 10-rule coding standard: `BaseEntity` inheritance, `ReqeustCommonDataBean` (intentional platform typo), `BaseCommonDAO_HI`, no `QueryWrapper`, `II{Entity}` service interfaces, FastJSON for save / Spring BeanUtils for update, `@CheckToken` on all endpoints, 7-language i18n, `ResponseMsgCode` enum (no hardcoded strings). These rules are enforced in `adspecs-tasks` and reference convention docs.
+
+### TDD Pipeline
+
+Task skills (`adspecs-tasks`, `adspecs-front-tasks`) follow strict RED→GREEN→REFACTOR ordering. Test tasks marked `[TDD]` must precede all implementation tasks within each user story phase.
+
+### Target Project Structure
+
+Projects initialized by this plugin follow this layout:
+
+| Directory                      | Purpose                                            |
+| ------------------------------ | -------------------------------------------------- |
+| `docs/20-prd/`                 | Requirements specs (PRD)                           |
+| `docs/30-system-design/`       | System design + SQL + frontend design + task lists |
+| `docs/40-project_conventions/` | ECP coding standards                               |
+| `.adspecs/templates/`          | Standard document templates                        |
+| `web-ui/`                      | Frontend production project                        |
+| `service/`                     | Backend Java service modules                       |
+| `front-demo/`                  | PM design-phase Vue 3 demo project                 |
+
+## External Dependencies
+
+This plugin requires the **superpowers** plugin for coding-phase skills:
+- `subagent-driven-development` — Subagent-driven parallel development
+- `test-driven-development` — RED → GREEN → REFACTOR TDD cycle
+- `verification-before-completion` — Pre-completion verification
+- `finishing-a-development-branch` — Branch cleanup / PR creation
+
+## Installation & Distribution
+
+```bash
+# Register marketplace
+claude plugins marketplace add <path-to>/.claude-plugin --scope user|project
+
+# Install plugin
+claude plugins install adspecs --scope user|project
+```

package/INSTALL.md

@@ -0,0 +1,134 @@
+# 安装手册
+
+## 环境准备
+
+### 1. 安装 superpowers 插件（前置依赖）
+
+adspecs 的编码阶段依赖 `superpowers` 插件提供的 `subagent-driven-development`、`test-driven-development` 等通用 Skill，必须先安装：
+
+**方式 A：官方市场（推荐）**
+
+```txt
+/plugin install superpowers@claude-plugins-official
+```
+
+**方式 B：第三方市场**
+
+```txt
+# 第一步：注册市场
+/plugin marketplace add obra/superpowers-marketplace
+
+# 第二步：从该市场安装插件
+/plugin install superpowers@superpowers-marketplace
+```
+
+### 2. 安装 AdSpecs 插件
+
+adspecs 插件提供**用户级**和**项目级**两种安装方式，按需选择：
+
+| 安装方式   | 作用范围           | 存储位置                             | 适用场景                         |
+| ---------- | ------------------ | ------------------------------------ | -------------------------------- |
+| **用户级** | 当前用户的所有项目 | `~/.claude/plugins/adspecs/`         | 个人开发者，多个项目共用同一插件 |
+| **项目级** | 仅当前项目         | `{project}/.claude/plugins/adspecs/` | 团队协作，插件随项目版本控制     |
+
+#### 方式 A：用户级安装（推荐个人开发者）
+
+插件安装到用户主目录，所有项目均可使用，无需每个项目重复安装。
+
+```txt
+# 第一步：注册用户级 marketplace
+claude plugins marketplace add <adspecs-marketplace-path> --scope user
+
+# 第二步：安装插件（用户级）
+claude plugins install adspecs --scope user
+```
+
+**效果**：安装完成后，任意目录下启动 Claude Code 均可使用 adspecs 的全部 Skill。
+
+**卸载**：
+
+```txt
+claude plugins uninstall adspecs --scope user
+```
+
+#### 方式 B：项目级安装（推荐团队协作）
+
+插件安装到当前项目目录，仅在当前项目中生效，可随项目代码一起纳入版本控制。
+
+```txt
+# 第一步：进入项目根目录
+cd /path/to/your/project
+
+# 第二步：注册项目级 marketplace
+claude plugins marketplace add <adspecs-marketplace-path> --scope project
+
+# 第三步：安装插件（项目级）
+claude plugins install adspecs --scope project
+```
+
+**效果**：仅在当前项目目录下可使用 adspecs 的 Skill，其他项目不受影响。
+
+**版本控制**（可选）：如需团队共享插件配置，将 `.claude/plugins/` 目录提交到 Git 仓库：
+
+```bash
+# .gitignore 中不要忽略 .claude/plugins/ 目录
+git add .claude/plugins/
+git commit -m "chore: add adspecs plugin configuration"
+```
+
+**卸载**：
+
+```txt
+claude plugins uninstall adspecs --scope project
+```
+
+#### 方式 C：从 Git 仓库安装
+
+若未配置 adspecs marketplace，可直接从 Git 拉取插件源码后按本地 marketplace 安装。
+
+Git 地址：`https://gitee.com/yuebon/adspecs`
+
+**用户级安装示例**：
+
+```txt
+# 第一步：克隆仓库到本地（示例目录）
+git clone https://gitee.com/yuebon/adspecs ~/.claude/plugins/adspecs
+
+# 第二步：注册用户级 marketplace（指向仓库内 .claude-plugin）
+claude plugins marketplace add ~/.claude/plugins/adspecs --scope user
+
+# 第三步：安装 adspecs 插件（用户级）
+claude plugins install adspecs --scope user
+```
+
+**项目级安装示例**：
+
+```txt
+# 第一步：进入项目根目录
+cd /path/to/your/project
+
+# 第二步：将插件仓库拉取到项目内（示例目录）
+git clone https://gitee.com/yuebon/adspecs ./.claude/plugins/adspecs
+
+# 第三步：注册项目级 marketplace（指向仓库内 .claude-plugin）
+claude plugins marketplace add ./.claude/plugins/adspecs --scope project
+
+# 第四步：安装 adspecs 插件（项目级）
+claude plugins install adspecs --scope project
+
+# 用户级升级
+claude plugins update adspecs --scope user
+
+# 项目级升级
+claude plugins update adspecs --scope project
+```
+
+#### 选择建议
+
+- **个人开发者，维护多个项目** → 选**用户级**，一次安装全局生效
+- **团队协作，需要统一插件版本** → 选**项目级**，插件随代码版本控制
+- **同时存在两种需求** → 两种可同时安装，项目级优先于用户级（就近原则）
+
+> **注意**：安装完成后，建议重启 Claude Code 以确保所有 Skill 被正确加载。如遇到 Skill 未生效，可执行 `/plugins` 查看当前已加载的插件列表。
+
+---