@niujiajie/freespec 0.0.0-stage → 1.15.0

package/dist/utils/task-progress.d.ts

@@ -0,0 +1,67 @@
+export interface ParsedTask {
+    /** Checkbox state: `[x]`/`[X]` is done, every other marker (and none) is not. */
+    done: boolean;
+    /** Task text after the checkbox, trimmed (may be empty). */
+    description: string;
+}
+/**
+ * Parses every task line in a tasks file, in document order.
+ *
+ * Every line matching the pattern counts, wherever it sits - inside a code
+ * fence, an HTML comment or an indented block, as before. Skipping fenced
+ * checkboxes was tried and dropped: every rule for deciding which fence is
+ * "real" has an input where a stray or unbalanced ``` swallows genuine tasks.
+ * Counting a documented example as work is a loud, bypassable false positive;
+ * losing a real task is a silent one.
+ */
+export declare function parseTaskLines(content: string): ParsedTask[];
+export interface TaskProgress {
+    total: number;
+    completed: number;
+}
+export declare function countTasksFromContent(content: string): TaskProgress;
+/**
+ * Run-scoped memo mapping a schema name to its tracked-tasks `generates` glob.
+ * When one command resolves progress for many changes under a constant
+ * `projectRoot` — e.g. `validate --archived` over an append-only archive — this
+ * avoids re-reading and re-parsing (YAML + Zod) the same `schema.yaml` once per
+ * change. Keyed by schema name alone, which is safe *only* because a single run
+ * holds `projectRoot` constant; never reuse one cache across differing roots.
+ */
+export type SchemaGlobCache = Map<string, string | undefined>;
+/** Resolves the task files selected by the schema's apply tracking rule. */
+export declare function resolveTaskFilesForChange(changeDir: string, projectRoot: string, schemaGlobCache?: SchemaGlobCache): string[];
+export interface TaskProgressDetail extends TaskProgress {
+    /**
+     * Task files that exist but could not be read (any error other than ENOENT).
+     * `getTaskProgressForChange` discards this list to preserve its behavior;
+     * callers that must fail loudly on an unreadable tasks file — e.g.
+     * `freespec validate --archived` — read it so an unreadable file is never
+     * silently counted as "no tasks" (#205).
+     */
+    unreadable: string[];
+}
+/**
+ * Computes a change's task progress by resolving its tracked-tasks artifact and
+ * counting checkboxes across every file matched by that artifact's `generates`
+ * glob — the same file-resolution `freespec status` uses to detect the tasks
+ * artifact (`resolveArtifactOutputs`) — so progress is no longer blind to nested
+ * `tasks.md` files (#1202). Falls back to a single top-level `tasks.md` (exactly
+ * as before) when the schema is unresolvable, no tracked-tasks artifact is found,
+ * or the glob matches no file. Also reports task files that exist but could not
+ * be read. Per-file read errors are captured (never thrown); the only throw path
+ * is a malformed/unsafe schema whose glob resolution rejects (path traversal or
+ * a linked-directory cycle in `resolveArtifactOutputs`). Pass `schemaGlobCache`
+ * to memoize schema→glob resolution across many changes in one run.
+ */
+export declare function getTaskProgressDetailForChange(changesDir: string, changeName: string, projectRoot: string, schemaGlobCache?: SchemaGlobCache): Promise<TaskProgressDetail>;
+/**
+ * The task-completion counter `status`, `list`, and `archive` share. Delegates
+ * to `getTaskProgressDetailForChange` and drops the `unreadable` detail, so its
+ * returned totals are unchanged. Throws only on the same malformed/unsafe-schema
+ * glob-resolution path as that function (existing behavior; callers guard it as
+ * they did before).
+ */
+export declare function getTaskProgressForChange(changesDir: string, changeName: string, projectRoot: string): Promise<TaskProgress>;
+export declare function formatTaskStatus(progress: TaskProgress): string;
+//# sourceMappingURL=task-progress.d.ts.map

package/dist/utils/task-progress.js

@@ -0,0 +1,184 @@
+import { promises as fs } from 'fs';
+import path from 'path';
+import { resolveArtifactOutputs, resolveSchema } from '../core/artifact-graph/index.js';
+import { resolveSchemaForChange } from './change-metadata.js';
+/**
+ * A Markdown task line: a list item carrying a checkbox that holds at most one
+ * non-whitespace marker - `[ ]`, `[x]`, `[]`, `[~]`, `[ x ]` all qualify - under
+ * any CommonMark list marker - `-`, `*`, `+`, or an ordered `1.` / `1)` of up
+ * to nine digits. Reading only `-` and `*` left an unchecked `1. [ ]` or
+ * `+ [ ]` task out of every count, so archive reported "✓ Complete" over it.
+ *
+ * Leading whitespace is allowed so nested sub-tasks count like their parents.
+ * Anchoring at column 0 made `  - [ ] 1.1.1 ...` invisible to progress, to the
+ * apply task list, and to archive's incomplete-task check, so a change with
+ * unfinished sub-tasks reported "✓ Complete" and archived without a warning.
+ *
+ * The marker is no longer restricted to ` `/`x`/`X`, because a checkbox this
+ * pattern rejects is a line that counts toward neither the numerator nor the
+ * denominator: a tasks.md whose remaining work was written `- [~] ...`
+ * reported "✓ Complete" and archived with no incomplete-task warning, and
+ * marking items `[~]` *shrank* the denominator instead of leaving them counted
+ * as not-done (#1761). An empty `[]` and a padded `[ x]` were lost the same
+ * silent way. Only `x`/`X` means done, so every unrecognised marker reads as
+ * not-done - the conservative default, and no new concept: FreeSpec does not
+ * adopt `[~]` or any other marker's meaning, it just stops dropping the line.
+ *
+ * Permissive on purpose, and safe to keep that way: any character class
+ * tightened here drops lines that used to count, and a task this parser drops
+ * is a task `freespec archive` stops warning about. The cost of the wide class
+ * is over-counting - `- [1] ...` in a tasks file now reads as one unfinished
+ * task - which is a loud, correctable false positive, unlike the silent loss.
+ *
+ * Where the width stops, and why: the marker is one token, so a *multi*
+ * character bracket stays unmatched. Widening to `[^\]]*` would swallow the
+ * commonest bullet in Markdown - `- [Some doc](./doc.md)`, whose `]` is
+ * followed by `(`, not by a space - and turn every link list into phantom
+ * unfinished work. A dropped `- [WIP] ...` is the accepted residue of keeping
+ * link bullets out; report it as a bug in this trade, not in the marker set.
+ *
+ * One-character labels need the same guard, which the width alone does not
+ * give: `- [A](https://example.com)` and `- [1](./one)` are a link bullet and
+ * a reference-link bullet, not tasks, yet their label is a single token and
+ * would match. So the closing bracket may not be followed by `(` or `[`, the
+ * only two characters that continue Markdown link syntax. A checkbox is
+ * followed by its description or by end of line, and `- [x]done` still parses.
+ * The one exception is a whitespace-only box: `- [ ](...)` and `- [ ][...]`
+ * matched the strict pattern as unfinished tasks, so they still count. The guard
+ * may drop only lines that could never hide open work.
+ *
+ * Deliberately unanchored at the end: `.` does not match `\r`, so writing the
+ * description group as `(.*)$` would reject every line of a CRLF tasks.md.
+ */
+const TASK_LINE_PATTERN = /^\s*(?:[-*+]|\d{1,9}[.)])\s*\[(?:\s*([^\]\s]?)\s*\](?![([])|\s+\])\s*(.*)/;
+/**
+ * Parses every task line in a tasks file, in document order.
+ *
+ * Every line matching the pattern counts, wherever it sits - inside a code
+ * fence, an HTML comment or an indented block, as before. Skipping fenced
+ * checkboxes was tried and dropped: every rule for deciding which fence is
+ * "real" has an input where a stray or unbalanced ``` swallows genuine tasks.
+ * Counting a documented example as work is a loud, bypassable false positive;
+ * losing a real task is a silent one.
+ */
+export function parseTaskLines(content) {
+    const tasks = [];
+    for (const line of content.split('\n')) {
+        const match = line.match(TASK_LINE_PATTERN);
+        if (match) {
+            tasks.push({ done: (match[1] ?? '').toLowerCase() === 'x', description: match[2].trim() });
+        }
+    }
+    return tasks;
+}
+export function countTasksFromContent(content) {
+    const tasks = parseTaskLines(content);
+    return {
+        total: tasks.length,
+        completed: tasks.filter((task) => task.done).length,
+    };
+}
+/**
+ * Identifies the change's tracked-tasks artifact: the artifact whose `generates`
+ * equals the schema's `apply.tracks` value, falling back to the artifact with id
+ * `tasks` when no `apply` block declares what it tracks. (`apply.tracks` is a
+ * filename that *selects* the artifact; the glob is that artifact's `generates`.)
+ */
+function findTrackedTasksArtifact(schema) {
+    const tracks = schema.apply?.tracks;
+    if (tracks != null) {
+        return schema.artifacts.find((a) => a.generates === tracks);
+    }
+    return schema.artifacts.find((a) => a.id === 'tasks');
+}
+/**
+ * Resolves the tracked-tasks artifact's output glob for a change, or undefined
+ * when the schema cannot be resolved or no tracked-tasks artifact exists.
+ * `resolveSchema` throws on an unresolvable/misnamed schema; we swallow that so
+ * the caller falls back to a single top-level `tasks.md` and never crashes.
+ * A `schemaGlobCache`, when supplied, memoizes the schema-name → glob lookup for
+ * the duration of one run.
+ */
+function resolveTrackedTasksGlob(changeDir, projectRoot, schemaGlobCache) {
+    try {
+        const schemaName = resolveSchemaForChange(changeDir, undefined, projectRoot);
+        if (schemaGlobCache?.has(schemaName))
+            return schemaGlobCache.get(schemaName);
+        const schema = resolveSchema(schemaName, projectRoot);
+        const generates = findTrackedTasksArtifact(schema)?.generates;
+        schemaGlobCache?.set(schemaName, generates);
+        return generates;
+    }
+    catch {
+        return undefined;
+    }
+}
+/** Resolves the task files selected by the schema's apply tracking rule. */
+export function resolveTaskFilesForChange(changeDir, projectRoot, schemaGlobCache) {
+    const generates = resolveTrackedTasksGlob(changeDir, projectRoot, schemaGlobCache);
+    return generates ? resolveArtifactOutputs(changeDir, generates) : [];
+}
+/**
+ * Reads one task file and counts its checkboxes. ENOENT (a glob file that
+ * vanished between resolve and read, or the absent single top-level `tasks.md`)
+ * means zero tasks, exactly as before. Any other error (permissions, I/O,
+ * ENOTDIR) is recorded in `unreadable` so a caller can surface it; the count
+ * still contributes zero, so existing callers see no change.
+ */
+async function countTaskFile(file, unreadable) {
+    try {
+        const content = await fs.readFile(file, 'utf-8');
+        return countTasksFromContent(content);
+    }
+    catch (error) {
+        if (error?.code !== 'ENOENT')
+            unreadable.push(file);
+        return { total: 0, completed: 0 };
+    }
+}
+/**
+ * Computes a change's task progress by resolving its tracked-tasks artifact and
+ * counting checkboxes across every file matched by that artifact's `generates`
+ * glob — the same file-resolution `freespec status` uses to detect the tasks
+ * artifact (`resolveArtifactOutputs`) — so progress is no longer blind to nested
+ * `tasks.md` files (#1202). Falls back to a single top-level `tasks.md` (exactly
+ * as before) when the schema is unresolvable, no tracked-tasks artifact is found,
+ * or the glob matches no file. Also reports task files that exist but could not
+ * be read. Per-file read errors are captured (never thrown); the only throw path
+ * is a malformed/unsafe schema whose glob resolution rejects (path traversal or
+ * a linked-directory cycle in `resolveArtifactOutputs`). Pass `schemaGlobCache`
+ * to memoize schema→glob resolution across many changes in one run.
+ */
+export async function getTaskProgressDetailForChange(changesDir, changeName, projectRoot, schemaGlobCache) {
+    const changeDir = path.join(changesDir, changeName);
+    const files = resolveTaskFilesForChange(changeDir, projectRoot, schemaGlobCache);
+    const targets = files;
+    const unreadable = [];
+    let total = 0;
+    let completed = 0;
+    for (const file of targets) {
+        const progress = await countTaskFile(file, unreadable);
+        total += progress.total;
+        completed += progress.completed;
+    }
+    return { total, completed, unreadable };
+}
+/**
+ * The task-completion counter `status`, `list`, and `archive` share. Delegates
+ * to `getTaskProgressDetailForChange` and drops the `unreadable` detail, so its
+ * returned totals are unchanged. Throws only on the same malformed/unsafe-schema
+ * glob-resolution path as that function (existing behavior; callers guard it as
+ * they did before).
+ */
+export async function getTaskProgressForChange(changesDir, changeName, projectRoot) {
+    const { total, completed } = await getTaskProgressDetailForChange(changesDir, changeName, projectRoot);
+    return { total, completed };
+}
+export function formatTaskStatus(progress) {
+    if (progress.total === 0)
+        return 'No tasks';
+    if (progress.completed === progress.total)
+        return '✓ Complete';
+    return `${progress.completed}/${progress.total} tasks`;
+}
+//# sourceMappingURL=task-progress.js.map

package/package.json

@@ -1,6 +1,76 @@
 {
   "name": "@niujiajie/freespec",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "1.15.0",
+  "description": "AI-native system for spec-driven development",
+  "keywords": [
+    "freespec",
+    "specs",
+    "cli",
+    "ai",
+    "development"
+  ],
+  "homepage": "https://gitee.com/niu_jiajie/openspec.git",
+  "repository": {
+    "type": "git",
+    "url": "https://gitee.com/niu_jiajie/openspec.git"
+  },
+  "license": "MIT",
+  "author": "FreeSpec Contributors",
+  "type": "module",
+  "packageManager": "pnpm@10.34.5",
+  "publishConfig": {
+    "access": "public"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    }
+  },
+  "bin": {
+    "freespec": "./bin/freespec.js"
+  },
+  "files": [
+    "dist",
+    "bin",
+    "schemas",
+    "skill-files",
+    "!dist/**/*.test.js",
+    "!dist/**/__tests__",
+    "!dist/**/*.map"
+  ],
+  "scripts": {
+    "lint": "eslint src/",
+    "build": "node build.js",
+    "generate:skills": "node scripts/generate-skillssh.mjs",
+    "dev": "tsc --watch",
+    "dev:cli": "pnpm build && node bin/freespec.js",
+    "prepare": "node build.js",
+    "prepublishOnly": "pnpm run build",
+    "check:pack-version": "node scripts/pack-version-check.mjs"
+  },
+  "engines": {
+    "node": ">=20.19.0"
+  },
+  "devDependencies": {
+    "@types/node": "^20.19.43",
+    "@types/picomatch": "^4.0.3",
+    "eslint": "^10.5.0",
+    "typescript": "^6.0.3",
+    "typescript-eslint": "^8.65.0"
+  },
+  "dependencies": {
+    "@inquirer/core": "^12.0.0",
+    "@inquirer/prompts": "^8.5.2",
+    "brace-expansion": "^5.0.12",
+    "chalk": "^5.6.2",
+    "commander": "^14.0.0",
+    "cross-spawn": "7.0.6",
+    "diff": "^9.0.0",
+    "ora": "^9.4.1",
+    "picomatch": "^4.0.4",
+    "tinyglobby": "^0.2.17",
+    "yaml": "^2.8.3",
+    "zod": "^4.4.3"
+  }
+}

package/schemas//351/273/230/350/256/244/schema.yaml

@@ -0,0 +1,68 @@
+name: 默认
+version: 1
+description: 四份中文文档都可选，没有先后依赖
+artifacts:
+  - id: requirements
+    generates: 需求文档.md
+    description: 给人看的需求说明
+    template: 需求文档.md
+    instruction: |
+      写 `需求文档.md`。文件可以没有。这次要写，就用模板里的四个标题，顺序不要换，都保留。需求待定没有项就写「无」。
+
+      每节写什么、句子多长、哪些词不能出现，以技能目录的 `references/文风.md` 为准。需求待定里写什么，以 `references/需求待定.md` 为准。
+
+      已经说清的写进背景、描述或功能点。会改功能点但还没定的，写进需求待定，把这份文档写完。不要编一个结果来填功能点，也不要为了这些缺口停下来重问。
+      有深思记录时，已定的写进对应的节，未决写进需求待定。句子用白话。
+    requires: []
+
+  - id: design
+    generates: 设计文档.md
+    description: 按章写的设计说明
+    template: 设计文档.md
+    instruction: |
+      写 `设计文档.md`。没有需求文档也可以写。章名、节名、表头都按 template 写，不要改成别的结构，不要把表写成段落。
+
+      模板是前后端的最大集合。用哪些章、标题下的「涉及：」留哪一个，只按技能目录的 `references/类型.md`。用到的章才写，从第一章连续编号。没用到的章整章删掉。
+      先看仓库里的真实代码再写变更方案。需求待定里会改变做法的，停下来问，不要在设计里补。
+      表、追溯和页面是否对得上，由技能目录的 `scripts/check-design.mjs` 判定。脚本未通过就不能交。护栏里写明脚本查不到的几条，人还要对过。
+    requires: []
+
+  - id: tasks
+    generates: 任务清单.md
+    description: 可勾选的执行清单
+    template: 任务清单.md
+    instruction: |
+      写 `任务清单.md`。没有需求文档或设计文档也可以写。有设计时按模板分组，没有对应章节的组整组删掉。
+
+      每条用简体中文写清做什么。禁止黑话和电报句。禁止：优化、完善、提升、大概、可能、后续再看，以及「实现某模块」「完成后端」。
+      一条对应一个接口加它的服务，或一张表，或一页。
+
+      每条任务用 `- [ ]` 开头。勾选只改成 `- [x]`，不要换别的符号。
+      一条里写清包含什么，以及对应哪条功能点、怎样算做完。没有需求文档时，写明这条对应这次说的哪一件事。
+      缓存、开关、线程池不要吞进一句模糊的话。
+      脚本写进仓库，和已经在数据库里执行过，要分开写。
+      已勾选的条目保留。
+      落盘前跑技能目录的 `scripts/check-tasks.mjs`。脚本未通过就不能交。
+    requires: []
+
+  - id: cases
+    generates: 测试用例.md
+    description: 要断言什么
+    template: 测试用例.md
+    instruction: |
+      写 `测试用例.md`。只写输入、操作、期望，不写某种语言的测试代码，不生成接口平台导入文件。
+
+      说明必须是简体中文，写清测什么、期望什么，不靠黑话。不要写 Given、When、Then。方法、路径、JSON 键保留原文。
+
+      一条行为一条用例。有接口时分开写正常、业务不允许、参数不合法；涉及登录或权限再写未登录、无权限。
+      期望要和已经写过的功能点一致。没有功能点就按这次说的写，并标明哪些是假设。需求待定里还没定的结果，不要写成用例里的期望。
+      可以跑的失败测试由「写Java」或以后的语言技能来落成文件并运行。
+      落盘前跑技能目录的 `scripts/check-cases.mjs`。脚本未通过就不能交。
+    requires: []
+
+apply:
+  requires: []
+  instruction: |
+    已有的需求文档、设计文档、任务清单、用例都可以当上下文。缺的文件不用补齐。
+    用用户点名的语言技能实现。有用例时，先把用例变成会失败的测试再写实现。
+    设计里某个方法没有步骤时，不要编算法，停下来问。

package/schemas//351/273/230/350/256/244/templates//344/273/273/345/212/241/346/270/205/345/215/225.md

@@ -0,0 +1,25 @@
+# 任务清单 · <变更名>
+
+> 对齐设计涉及范围：
+
+没有对应设计章节的组整组删掉，不要留空标题。已勾选的条目保留，不要重排后弄丢。
+
+## 1. 数据与配置
+
+- [ ] 1.1 （写清包含什么。缓存、开关、线程池、定时任务要单独能看出来，不要吞进一句「相关配置」。交付默认是仓库里的脚本，不是已经在库里执行过。对应功能点：）完成：
+
+## 2. 前端页面
+
+- [ ] 2.1 （对应设计里的哪一页。对应功能点：）完成：
+
+## 3. 接口
+
+- [ ] 3.1 （写明方法和路径。停用的接口写明删掉哪些调用。对应功能点：）完成：
+
+## 4. 服务
+
+- [ ] 4.1 （对应设计里该方法的步骤。设计只写了方法名、没有步骤时，不要在这里编算法。对应功能点：）完成：
+
+## 5. 测试
+
+- [ ] 5.1 （有用例时，对应哪几条用例。对应功能点：）完成：

package/schemas//351/273/230/350/256/244/templates//346/265/213/350/257/225/347/224/250/344/276/213.md

@@ -0,0 +1,34 @@
+# 用例 · <变更名>
+
+每条只写输入、操作、期望。不写某种语言的测试代码，不写接口平台导入文件。
+
+一条行为一条用例，不要合并。有接口时分开写：正常、业务不允许、参数不合法。需要登录或权限时再加未登录、无权限。
+
+## 核算
+
+| 验收条目 | 对应用例 | 还缺什么 |
+| :--- | :--- | :--- |
+| | | |
+
+## 用例
+
+### 正常
+
+#### C1
+
+- 输入：
+- 操作：
+- 期望：
+- 对应验收：
+
+### 业务不允许
+
+### 参数不合法
+
+### 未登录
+
+不涉及登录时删除本组。
+
+### 无权限
+
+不涉及权限时删除本组。

package/schemas//351/273/230/350/256/244/templates//350/256/276/350/256/241/346/226/207/346/241/243.md

@@ -0,0 +1,172 @@
+# <变更名> · 设计说明
+
+涉及：（纯前端、前后端、纯后端、仅数据或配置，只留一个）
+
+## 第一章 概述
+
+### 1.1 技术现状
+
+| 现在在哪 | 现在怎么做 | 依据文件 |
+| :--- | :--- | :--- |
+| | | |
+
+### 1.2 目的与边界
+
+| 类别 | 内容 | 对应功能点 |
+| :--- | :--- | :--- |
+| 要完成 | | |
+| 不做 | | |
+
+## 第二章 变更方案
+
+### 2.1 改动清单
+
+```text
+订单
+├── 改  订单接口
+├── 新  退款服务
+└── 前端
+    └── 改  订单详情页
+```
+
+| 层 | 文件 | 新/改/不动 | 动什么 | 追溯自 | 对应页面节 |
+| :--- | :--- | :--- | :--- | :--- | :--- |
+| Controller | | | | | 无 |
+| 前端 api | | | | | |
+| 组件 | | | | | |
+
+### 2.2 影响与测试关注
+
+| 影响谁 | 代码改没改 | 测试要盯什么 | 对应功能点 |
+| :--- | :--- | :--- | :--- |
+| | | | |
+
+### 2.3 取舍
+
+| 选了什么 | 另一个为什么不用 | 怎么回滚 |
+| :--- | :--- | :--- |
+| | | |
+
+## 第三章 数据与配置
+
+### 3.1 表结构
+
+| 库的种类 | |
+| :--- | :--- |
+| | |
+
+| 表 | 动作 | 索引 |
+| :--- | :--- | :--- |
+| | 新建或修改 | |
+
+```sql
+-- 每张表一块可执行语句。索引和上面的表写同一套。
+```
+
+| 顺序 | 目标表 | 写入什么 |
+| :---: | :--- | :--- |
+| | | |
+
+### 3.2 文件
+
+| 文件 | 用途 | 列（按顺序） | 格式 |
+| :--- | :--- | :--- | :--- |
+| | | | |
+
+### 3.3 其他配置
+
+| 类型 | 标识 | 默认值 | 环境差异 | 说明 |
+| :--- | :--- | :--- | :--- | :--- |
+| | | | | |
+
+## 第四章 前端页面原型设计
+
+### 4.1 （页面名）
+
+| 本页改动 | 引用接口 | 接口本次变化 |
+| :--- | :--- | :--- |
+| | | |
+
+```text
+┌─────────────────────┐
+│ 区域                 │
+│ [按钮]               │
+└─────────────────────┘
+```
+
+| 控件 | 选项文案 | 存库的码 |
+| :--- | :--- | :--- |
+| | | |
+
+| # | 规则 |
+| :---: | :--- |
+| 1 | |
+
+| 操作 | 方法 | 路径 |
+| :--- | :--- | :--- |
+| | | |
+
+## 第五章 接口设计
+
+### 5.1 接口清单
+
+| 请求方式 | 路径 | 作用 | 新增/修改 | 权限或登录 | 入口 | 所属改动点 |
+| :--- | :--- | :--- | :--- | :--- | :--- | :--- |
+| | | | | | | |
+
+### 5.2 接口详细设计
+
+#### 接口 N：方法 路径（新增或修改）
+
+| 对应功能点 | 数据范围 |
+| :--- | :--- |
+| | |
+
+请求参数：
+
+| 字段 | 位置 | 类型 | 长度 | 必填 | 默认值 | 规则 | 校验失败提示 |
+| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
+| | | | | | | | |
+
+成功响应：
+
+| 字段 | 类型 | 说明 |
+| :--- | :--- | :--- |
+| | | |
+
+业务错误：
+
+| 场景 | 错误码 | 提示信息 | 触发条件 |
+| :--- | :--- | :--- | :--- |
+| | | | |
+
+## 第六章 服务层设计
+
+### 6.1 接口与服务映射
+
+| 接口（或定时任务、消息） | 服务 | 方法 | 所属改动点 |
+| :--- | :--- | :--- | :--- |
+| | | | |
+
+### 6.2 方法详细设计
+
+#### （方法名）
+
+| 步骤 | 做什么 | 分支 |
+| :---: | :--- | :--- |
+| 1 | 校验参数是否齐全 | 缺了就停下，不保存 |
+| 2 | 校验这条用户记录是否已经存在 | 已存在则不再新增 |
+| 3 | 把登录密钥加密 | |
+| 4 | 把手机号加密 | |
+| 5 | 保存用户信息 | |
+| 6 | 保存用户关联的账户信息 | |
+
+| 事务 | 副作用 | 状态变化 |
+| :--- | :--- | :--- |
+| | | |
+
+## 修订记录
+
+| 版本 | 日期 | 修订人 | 修订内容 |
+| :---: | :--- | :--- | :--- |
+| v1.0 | | | 初稿 |

package/schemas//351/273/230/350/256/244/templates//351/234/200/346/261/202/346/226/207/346/241/243.md

@@ -0,0 +1,19 @@
+# <变更名> · 需求说明
+
+## 需求背景
+
+（现在谁办不到什么。不超过五句，只写现状。）
+
+## 需求描述
+
+这次让（谁）能（做成什么样）。（旁边哪些）这次不动。
+
+## 需求功能点拆分
+
+1. 新增（一件事）。（谁）在（哪里）做，看见（什么）。
+
+2. 修改（一件事）。做成（什么样）。
+
+## 需求待定
+
+无