@oevery/rsp 1.0.1 → 1.0.3

package/README.md

@@ -1,6 +1,6 @@
-# RSP: Rules, Spec, Plan
+# RSP: Rules, Specs, Plans
 
-RSP = **Rules, Spec, Plan** — a lightweight AI-assisted development workflow.
+RSP = **Rules, Specs, Plans** — a lightweight AI-assisted development workflow.
 
 ## Quick start
 
@@ -34,7 +34,7 @@ For other tools (Cursor, Claude Code, Copilot), add the path to the appropriate
 ├── config.yaml                # project config (custom statuses, priorities, sections)
 ├── rules/                     # technical constraints, long-lived
 │   └── rsp-rules.md
-├── spec/                      # project-level architecture
+├── specs/                     # project-level architecture
 │   └── INDEX.md               # extracted spec summaries from archived features
 ├── features/                  # feature files (flat or nested)
 │   ├── login.md

package/README.zh-CN.md

@@ -1,6 +1,6 @@
-# RSP：Rules, Spec, Plan
+# RSP：Rules, Specs, Plans
 
-RSP = **Rules（规则）、Spec（规格）、Plan（计划）** — 轻量级 AI 辅助开发工作流。
+RSP = **Rules（规则）、Specs（规格）、Plans（计划）** — 轻量级 AI 辅助开发工作流。
 
 ## 快速开始
 
@@ -33,7 +33,7 @@ cd my-project && rsp init
 .rsp/
 ├── config.yaml                # 项目配置
 ├── rules/                     # 技术约束
-├── spec/                      # 项目级架构
+├── specs/                     # 项目级架构
 │   └── INDEX.md               # 从归档提取的 spec 摘要
 ├── features/                  # 特性文件
 │   ├── auth/

package/bin/rsp.mjs

@@ -0,0 +1,5 @@
+#!/usr/bin/env node
+
+import { runCli } from '../dist/cli.mjs'
+
+runCli()

package/dist/cli.mjs

@@ -595,7 +595,7 @@ async function runCheckIfHasDependents(name) {
   }
 }
 async function updateSpecIndex(name, date) {
-  const specIndexPath = join5(RSP_DIR, "spec", "INDEX.md");
+  const specIndexPath = join5(RSP_DIR, "specs", "INDEX.md");
   const archiveDir = join5(RSP_DIR, "archive");
   const escaped = name.replace(/[-/\\^$*+?.()|[\]{}]/g, "\\$&");
   const lineRe = new RegExp(`^\\| \\d{4}-\\d{2}-\\d{2} \\| ${escaped} \\|`, "m");
@@ -626,7 +626,7 @@ async function updateSpecIndex(name, date) {
     if (lineRe.test(existing))
       return;
     if (!existing.includes("| Date | Feature | Summary |")) {
-      await writeFile3(specIndexPath, `# Spec Index
+      await writeFile3(specIndexPath, `# Specs Index
 
 | Date | Feature | Summary |
 |------|---------|---------|
@@ -721,10 +721,11 @@ async function detectProjectName() {
   return basename3(process.cwd());
 }
 var AGENTS_BODY = `## Collaboration Mode
-This project uses **RSP** (Rules, Spec, Plan) \u2014 see \`.rsp/rules/\` for the full workflow definition (start with \`rsp-rules.md\`).
+This project uses **RSP** (Rules, Specs, Plans) \u2014 see \`.rsp/rules/\` for the full workflow definition (start with \`rsp-rules.md\`).
 
 Key conventions:
 - \`.rsp/rules/\` \u2014 technical constraints and coding conventions
+- \`.rsp/specs/\` \u2014 project-level architecture and design reference
 - \`.rsp/features/<name>.md\` \u2014 feature definitions (spec + plan + tests)
 - \`.rsp/active.d/\` \u2014 currently active features (path = feature name)
 - \`.rsp/archive/\` \u2014 completed features
@@ -763,7 +764,7 @@ async function initProject() {
   return withRspLock("init", async () => {
     const dirs = [
       join7(RSP_DIR, "rules"),
-      join7(RSP_DIR, "spec"),
+      join7(RSP_DIR, "specs"),
       join7(RSP_DIR, "features"),
       join7(RSP_DIR, "archive")
     ];
@@ -780,9 +781,9 @@ async function initProject() {
       await writeFile4(configPath, CONFIG_TEMPLATE);
       created = true;
     }
-    const specIndexPath = join7(RSP_DIR, "spec", "INDEX.md");
+    const specIndexPath = join7(RSP_DIR, "specs", "INDEX.md");
     if (!existsSync7(specIndexPath)) {
-      await writeFile4(specIndexPath, "# Spec Index\n\n_Extracted from archived features._\n");
+      await writeFile4(specIndexPath, "# Specs Index\n\n_Extracted from archived features._\n");
       created = true;
     }
     const gitignorePath = join7(RSP_DIR, ".gitignore");
@@ -826,7 +827,7 @@ ${AGENTS_BODY}
   ${pc.green("RSP scaffolded.")}
 `);
       console.log(`  Created: .rsp/rules/
-           .rsp/spec/
+           .rsp/specs/
            .rsp/features/
            .rsp/archive/
            .rsp/.gitignore
@@ -1110,7 +1111,7 @@ async function runCli(rawArgs = process.argv.slice(2)) {
     meta: {
       name: "rsp",
       version,
-      description: "RSP (Rules, Spec, Plan) workflow for AI-assisted development"
+      description: "RSP (Rules, Specs, Plans) workflow for AI-assisted development"
     },
     subCommands: {
       "init": initCommand,

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@oevery/rsp",
   "type": "module",
-  "version": "1.0.1",
-  "description": "RSP (Rules, Spec, Plan) workflow for AI-assisted development",
+  "version": "1.0.3",
+  "description": "RSP (Rules, Specs, Plans) workflow for AI-assisted development",
   "author": "oevery",
   "license": "MIT",
   "homepage": "https://github.com/oevery/rsp#readme",
@@ -14,16 +14,17 @@
   "keywords": [
     "rsp",
     "rules",
-    "spec",
-    "plan",
+    "specs",
+    "plans",
     "ai",
     "coding",
     "workflow"
   ],
   "bin": {
-    "rsp": "./dist/cli.mjs"
+    "rsp": "bin/rsp.mjs"
   },
   "files": [
+    "bin/",
     "dist/",
     "rules/"
   ],

package/rules/rsp-rules.md

@@ -5,14 +5,14 @@ description: RSP rules for Rules, Spec, and Plan driven development.
 
 # RSP
 
-RSP = Rules, Spec, Plan.
+RSP = Rules, Specs, Plans.
 
 ## Structure
 
 ```text
 .rsp/
 ├── rules/                    # technical constraints, long-lived
-├── spec/                     # project-level architecture (optional)
+├── specs/                    # project-level architecture (optional)
 ├── features/                 # active features
 │   ├── <name>.md             # or <domain>/<name>.md for grouping
 ├── active.d/                 # active feature markers
@@ -25,7 +25,7 @@ RSP = Rules, Spec, Plan.
 ## File roles
 
 - `rules/` — stable technical constraints, coding conventions, architecture decisions. One or more files, split by domain (e.g., `frontend.md`, `api.md`). Do not put business requirements here.
-- `spec/` — project-level architecture and design reference. Use for cross-cutting concerns, system diagrams, ADRs. Per-feature details go in `features/`.
+- \`specs/\` — project-level architecture and design reference. Use for cross-cutting concerns, system diagrams, ADRs. Per-feature details go in \`features/\`.
 - `features/<name>.md` — a complete feature definition, optionally grouped by domain subdirectory (e.g., `features/auth/login.md`). Contains YAML frontmatter, `## Spec` (what), `## Plan` (how), `## Tests`, and optional `## Notes`.
 - `active.d/` — active feature tracking. Mirrors the `features/` directory structure (e.g., `active.d/payments/checkout`). Each file is an empty marker; the file path is the source of truth. All features in `active.d/` are considered active.
 
@@ -36,7 +36,7 @@ RSP = Rules, Spec, Plan.
 3. If empty, ask the user or suggest `rsp new <name>`.
 4. Read the referenced `features/<name>.md`.
 5. Read `rules/` for technical constraints.
-6. Optionally read `spec/` for architecture context and `config.yaml` for customized statuses/priorities.
+6. Optionally read \`specs/\` for architecture context and \`config.yaml\` for customized statuses/priorities.
 
 ## Token optimization