specline 1.3.3 → 1.3.4

package/cli.mjs

@@ -368,7 +368,6 @@ function cmd_init(targetPath) {
   // 创建目录结构
   const dirs = [
     '.cursor/agents',
-    '.cursor/commands',
     '.cursor/skills',
     '.cursor/hooks',
     'specline/changes/archive',
@@ -404,12 +403,11 @@ function cmd_init(targetPath) {
   }
 
   const agentsCount = countFiles(join(target, '.cursor', 'agents'));
-  const commandsCount = countFiles(join(target, '.cursor', 'commands'));
   const skillsCount = countFiles(join(target, '.cursor', 'skills'));
   const hooksCount = countFiles(join(target, '.cursor', 'hooks'));
 
   success('Specline 初始化完成');
-  log(`📁 文件: ${commandsCount} commands, ${skillsCount} skills, ${agentsCount} agents, ${hooksCount} hooks`);
+  log(`📁 文件: ${skillsCount} skills, ${agentsCount} agents, ${hooksCount} hooks`);
   log('');
   log('🚀 试试在 Cursor 中输入:');
   log('   /specline-pipeline "你的第一个需求"');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specline",
-  "version": "1.3.3",
+  "version": "1.3.4",
   "description": "Spec-driven AI coding pipeline with deterministic quality gates for Cursor IDE",
   "bin": {
     "specline": "./cli.mjs"

package/templates/.cursor/commands/specline-explore.md

@@ -1,182 +0,0 @@
----
-name: /specline-explore
-id: specline-explore
-category: Workflow
-description: "Enter explore mode - think through ideas, investigate problems, clarify requirements"
----
-
-## ⚠️ 硬边界：探索模式禁止直接写代码
-
-**你只能做这些**：读取代码、画图、提问、比较方案、质疑假设、创建 Specline artifacts（proposal/design/specs）
-**你不能做这些**：写入/修改任何实现代码文件（Write、StrReplace、Delete、Shell 等会导致代码变更的操作）
-
-如果用户要你写代码 → 提醒退出探索模式，先 `/specline-pipeline` 或 `/specline-quickfix`。
-
----
-
-Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
-
-**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create Specline artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.
-
-**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
-
-**Input**: The argument after `/specline-explore` is whatever the user wants to think about. Could be:
-- A vague idea: "real-time collaboration"
-- A specific problem: "the auth system is getting unwieldy"
-- A change name: "add-dark-mode" (to explore in context of that change)
-- A comparison: "postgres vs sqlite for this"
-- Nothing (just enter explore mode)
-
----
-
-## The Stance
-
-- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
-- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
-- **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking
-- **Adaptive** - Follow interesting threads, pivot when new information emerges
-- **Patient** - Don't rush to conclusions, let the shape of the problem emerge
-- **Grounded** - Explore the actual codebase when relevant, don't just theorize
-
----
-
-## What You Might Do
-
-Depending on what the user brings, you might:
-
-**Explore the problem space**
-- Ask clarifying questions that emerge from what they said
-- Challenge assumptions
-- Reframe the problem
-- Find analogies
-
-**Investigate the codebase**
-- Map existing architecture relevant to the discussion
-- Find integration points
-- Identify patterns already in use
-- Surface hidden complexity
-
-**Compare options**
-- Brainstorm multiple approaches
-- Build comparison tables
-- Sketch tradeoffs
-- Recommend a path (if asked)
-
-**Visualize**
-```
-┌─────────────────────────────────────────┐
-│     Use ASCII diagrams liberally        │
-├─────────────────────────────────────────┤
-│                                         │
-│      ┌────────┐         ┌────────┐      │
-│      │ State  │────────▶│ State  │      │
-│      │   A    │         │   B    │      │
-│      └────────┘         └────────┘      │
-│                                         │
-│   System diagrams, state machines,      │
-│   data flows, architecture sketches,    │
-│   dependency graphs, comparison tables  │
-│                                         │
-└─────────────────────────────────────────┘
-```
-
-**Surface risks and unknowns**
-- Identify what could go wrong
-- Find gaps in understanding
-- Suggest spikes or investigations
-
----
-
-## Specline Awareness
-
-You have full context of the Specline system. Use it naturally, don't force it.
-
-### Check for context
-
-At the start, quickly check what exists:
-```bash
-specline-pipeline-gate.sh list --json
-```
-
-This tells you:
-- If there are active changes
-- Their names, schemas, and status
-- What the user might be working on
-
-If the user mentioned a specific change name, read its artifacts for context.
-
-### When no change exists
-
-Think freely. When insights crystallize, you might offer:
-
-- "This feels solid enough to start a change. Want me to create a proposal?"
-- Or keep exploring - no pressure to formalize
-
-### When a change exists
-
-If the user mentions a change or you detect one is relevant:
-
-1. **Read existing artifacts for context**
-   - `specline/changes/<name>/proposal.md`
-   - `specline/changes/<name>/design.md`
-   - `specline/changes/<name>/tasks.md`
-   - etc.
-
-2. **Reference them naturally in conversation**
-   - "Your design mentions using Redis, but we just realized SQLite fits better..."
-   - "The proposal scopes this to premium users, but we're now thinking everyone..."
-
-3. **Offer to capture when decisions are made**
-
-    | Insight Type               | Where to Capture               |
-    |----------------------------|--------------------------------|
-    | New requirement discovered | `specs/<capability>/spec.md` |
-    | Requirement changed        | `specs/<capability>/spec.md` |
-    | Design decision made       | `design.md`                  |
-    | Scope changed              | `proposal.md`                |
-    | New work identified        | `tasks.md`                   |
-    | Assumption invalidated     | Relevant artifact              |
-
-   Example offers:
-   - "That's a design decision. Capture it in design.md?"
-   - "This is a new requirement. Add it to specs?"
-   - "This changes scope. Update the proposal?"
-
-4. **The user decides** - Offer and move on. Don't pressure. Don't auto-capture.
-
----
-
-## What You Don't Have To Do
-
-- Follow a script
-- Ask the same questions every time
-- Produce a specific artifact
-- Reach a conclusion
-- Stay on topic if a tangent is valuable
-- Be brief (this is thinking time)
-
----
-
-## Ending Discovery
-
-There's no required ending. Discovery might:
-
-- **Flow into a proposal**: "Ready to start? I can create a change proposal."
-- **Result in artifact updates**: "Updated design.md with these decisions"
-- **Just provide clarity**: User has what they need, moves on
-- **Continue later**: "We can pick this up anytime"
-
-When things crystallize, you might offer a summary - but it's optional. Sometimes the thinking IS the value.
-
----
-
-## Guardrails
-
-- **Don't implement** - Never write code or implement features. Creating Specline artifacts is fine, writing application code is not.
-- **Don't fake understanding** - If something is unclear, dig deeper
-- **Don't rush** - Discovery is thinking time, not task time
-- **Don't force structure** - Let patterns emerge naturally
-- **Don't auto-capture** - Offer to save insights, don't just do it
-- **Do visualize** - A good diagram is worth many paragraphs
-- **Do explore the codebase** - Ground discussions in reality
-- **Do question assumptions** - Including the user's and your own

package/templates/.cursor/commands/specline-pipeline.md

@@ -1,22 +0,0 @@
----
-name: /specline-pipeline
-id: specline-pipeline
-category: Workflow
-description: 开发流水线元 Skill —— 编排 Spec → Coding → Review → Test → Archive 全流程
----
-
-开发流水线，自动编排从需求到归档的全流程。
-
-**用法：**
-- `/specline-pipeline <自然语言需求>` — 新建流水线
-- `/specline-pipeline --change <change-name>` — 恢复指定流水线
-- `/specline-pipeline` — 列出所有未完成流水线，选择继续
-
-**阶段：**
-1. Spec 编写与审核（specline-spec-creator 生成 → specline-spec-reviewer 审核）
-2. Coding 编码（基于 tasks.md 任务依赖分批并发）
-3. Code Review 审查（specline-code-reviewer）
-4. Test 测试链（单元 → 集成 → E2E，测试 Agent 为黑盒）
-5. Archive 归档
-
-每个阶段有确定性门禁（exit code 判定，零 LLM 参与），3 个人工检查点（Spec 确认、Review 复核、归档确认）。支持断点续跑。

package/templates/.cursor/commands/specline-quickfix.md

@@ -1,24 +0,0 @@
----
-name: /specline-quickfix
-id: specline-quickfix
-category: Workflow
-description: 轻量修改 Skill —— 小改动用 quickfix，大功能用 pipeline
----
-
-轻量修改流程，在不创建规划文档的情况下快速执行小改动。
-
-**用法：**
-- `/specline-quickfix <描述>` — 执行轻量修改流程（修 bug、改配置、文档微调等小改动）
-
-**阶段：**
-1. UNDERSTAND — 读取相关代码，理解变更上下文
-2. IMPLEMENT — 直接编辑文件（单 Agent，无子 Agent）
-3. REVIEW — ReadLints 自动校验 + 修复（最多 2 次）+ Agent 自审
-4. TEST — 运行项目已有单元测试（失败修复最多 2 次），无测试则跳过
-5. ARCHIVE — 生成 summary.md + files-changed.json，询问 git commit
-
-**适用场景**：1-3 个文件改动、单一关注点、不涉及架构变更、不需要新测试。
-
-**不适合的场景**（应使用 `/specline-pipeline`）：4+ 个文件改动、新增功能/重构、需要新测试、跨模块/多关注点。
-
-0 个人工确认点，全程自动质量保证。