spec-feature 1.0.6 → 1.0.7

package/README.md

@@ -113,16 +113,16 @@ To create a feature specification, use the `spec/feature.md` template with any A
 
 ### 📝 Input parameter format
 
-Pass parameters in one line in the format `@<feature>@ <context>`:
+Pass parameters in one line in the format `#<feature># <context>`:
 
-- the value between the first two `@` symbols is used as **FEATURE** and determines the feature folder (`@payments@` → `spec/features/payments`);
-- everything following the second `@` is **CONTEXT**. It can span multiple lines, include lists, links, and additional clarifications.
+- the value between the first two `#` symbols is used as **FEATURE** and determines the feature folder (`#payments#` → `spec/features/payments`);
+- everything following the second `#` is **CONTEXT**. It can span multiple lines, include lists, links, and additional clarifications.
 
 ### 🚀 Usage example
 
 ```
 Use the template from spec/feature.md.
-@user-auth@ Need to add user authentication via email and password. The user should be able to register, log in, and recover their password. Integration with the existing notification system is mandatory.
+#user-auth# Need to add user authentication via email and password. The user should be able to register, log in, and recover their password. Integration with the existing notification system is mandatory.
 ```
 
 ### ✨ What happens next
@@ -181,7 +181,7 @@ To update an existing feature, reuse `spec/feature.md`, specifying the name of t
 **📝 Update example:**
 ```
 Use the template from spec/feature.md.
-@user-auth@ Add two-factor authentication (2FA) via SMS. The user should be able to enable/disable 2FA in profile settings. Integration with existing SMS provider.
+#user-auth# Add two-factor authentication (2FA) via SMS. The user should be able to enable/disable 2FA in profile settings. Integration with existing SMS provider.
 ```
 
 The AI assistant will correctly overwrite `spec.md`, `plan.md`, and `tasks.md`, preserving the structure and updating the content for new requirements.
@@ -191,7 +191,7 @@ The AI assistant will correctly overwrite `spec.md`, `plan.md`, and `tasks.md`,
 ### 🚨 Common problems and solutions
 
 **❌ Problem:** AI assistant doesn't create feature folder
-- **✅ Solution:** Make sure you're using the correct format `@feature@ context` and that the assistant has file creation permissions
+- **✅ Solution:** Make sure you're using the correct format `#feature# context` and that the assistant has file creation permissions
 
 **❌ Problem:** Tasks are executed in wrong order
 - **✅ Solution:** Check task numbering in `tasks.md` and reorder if necessary
@@ -203,4 +203,4 @@ The AI assistant will correctly overwrite `spec.md`, `plan.md`, and `tasks.md`,
   ```
 
 **❌ Problem:** Conflict when updating existing feature
-- **✅ Solution:** Create a backup of current files before updating or use git to track changes
+- **✅ Solution:** Create a backup of current files before updating or use git to track changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spec-feature",
-  "version": "1.0.6",
+  "version": "1.0.7",
   "bin": {
     "spec-feature": "./bin/cli.js"
   },

package/spec/core/hotfix.md

@@ -4,8 +4,8 @@ Template automates feature maintenance after release: records hotfixes and synch
 
 **Parameters**
 
-- **FEATURE** — name of the folder with feature artifacts. Determined by the value between the first two `@` symbols (e.g., `@billing@` → `billing`).
-- **CONTEXT** — essence of the hotfix and expected result. This is everything passed after the second `@`; multi-line descriptions with links to incidents or PRs are allowed.
+- **FEATURE** — name of the folder with feature artifacts. Determined by the value between the first two `#` symbols (e.g., `#billing#` → `billing`).
+- **CONTEXT** — essence of the hotfix and expected result. This is everything passed after the second `#`; multi-line descriptions with links to incidents or PRs are allowed.
 
 **General rules**
 
@@ -32,4 +32,4 @@ Template automates feature maintenance after release: records hotfixes and synch
 3. Update `tasks.md`: add or adjust tasks, set checkboxes based on actual execution, supplement with verification requirements.
 4. Ensure all modified documents are complete and ready for implementation.
 
-Write strictly in Markdown. Goal — automatically bring all feature artifacts up to date under the hotfix and synchronize checklists with actual state.
+Write strictly in Markdown. Goal — automatically bring all feature artifacts up to date under the hotfix and synchronize checklists with actual state.

package/spec/core/plan.md

@@ -4,8 +4,8 @@ Template helps format the feature implementation plan in the **spec-feature** pr
 
 **Parameters**
 
-- **FEATURE** — name of the folder where the plan will be saved. Taken from the value between the first two `@` symbols (e.g., `@payments@` → `payments`).
-- **CONTEXT** — main context for preparing the plan. Consider everything after the second `@` in the parameter line; context can span multiple lines and include additional clarifications.
+- **FEATURE** — name of the folder where the plan will be saved. Taken from the value between the first two `#` symbols (e.g., `#payments#` → `payments`).
+- **CONTEXT** — main context for preparing the plan. Consider everything after the second `#` in the parameter line; context can span multiple lines and include additional clarifications.
 
 **General rules**
 
@@ -52,4 +52,4 @@ Template helps format the feature implementation plan in the **spec-feature** pr
 
 ```
 
-Write strictly in Markdown and automatically create/update the plan file. **Goal** — create/update file `/spec/features/{FEATURE}/plan.md` describing HOW we implement the feature based on **CONTEXT**.
+Write strictly in Markdown and automatically create/update the plan file. **Goal** — create/update file `/spec/features/{FEATURE}/plan.md` describing HOW we implement the feature based on **CONTEXT**.

package/spec/core/spec.md

@@ -4,8 +4,8 @@ Template helps describe a feature before implementation in the **spec-feature**
 
 **Parameters**
 
-- **FEATURE** — name of the folder where the specification will be saved. Taken from the value between the first two `@` symbols (e.g., `@payments@` → `payments`).
-- **CONTEXT** — main context for describing the feature. Consider everything after the second `@` in the parameter line; context can span multiple lines and include additional clarifications.
+- **FEATURE** — name of the folder where the specification will be saved. Taken from the value between the first two `#` symbols (e.g., `#payments#` → `payments`).
+- **CONTEXT** — main context for describing the feature. Consider everything after the second `#` in the parameter line; context can span multiple lines and include additional clarifications.
 
 **General rules**
 
@@ -48,4 +48,4 @@ Template helps describe a feature before implementation in the **spec-feature**
 
 ```
 
-Write strictly in Markdown and automatically create/update the specification file. **Goal** — create/update file `/spec/features/{FEATURE}/spec.md` describing WHAT we do and WHY, based on **CONTEXT**.
+Write strictly in Markdown and automatically create/update the specification file. **Goal** — create/update file `/spec/features/{FEATURE}/spec.md` describing WHAT we do and WHY, based on **CONTEXT**.

package/spec/core/tasks.md

@@ -4,8 +4,8 @@ Template helps form a task list for feature implementation in the **spec-feature
 
 **Parameters**
 
-- **FEATURE** — name of the folder where the task list will be saved. Taken from the value between the first two `@` symbols (e.g., `@payments@` → `payments`).
-- **CONTEXT** — main context for preparing tasks. Consider everything after the second `@` in the parameter line; context can span multiple lines and include additional clarifications.
+- **FEATURE** — name of the folder where the task list will be saved. Taken from the value between the first two `#` symbols (e.g., `#payments#` → `payments`).
+- **CONTEXT** — main context for preparing tasks. Consider everything after the second `#` in the parameter line; context can span multiple lines and include additional clarifications.
 
 **General rules**
 
@@ -56,4 +56,4 @@ Template helps form a task list for feature implementation in the **spec-feature
 
 ```
 
-Write strictly in Markdown and automatically create/update the task list file. Do not proceed to task execution without a separate request. **Goal** — create/update file `/spec/features/{FEATURE}/tasks.md` with a list of WHAT we do and how we verify the result, based on **CONTEXT** and prepared materials.
+Write strictly in Markdown and automatically create/update the task list file. Do not proceed to task execution without a separate request. **Goal** — create/update file `/spec/features/{FEATURE}/tasks.md` with a list of WHAT we do and how we verify the result, based on **CONTEXT** and prepared materials.

package/spec/core/verify.md

@@ -4,8 +4,8 @@ Template helps format the results of automatic task execution verification and m
 
 **Parameters**
 
-- **FEATURE** — name of the folder where the verification report will be saved. Taken from the value between the first two `@` symbols (e.g., `@payments@` → `payments`).
-- **CONTEXT** — main context and verification purpose. Consider everything after the second `@` in the parameter line; context can span multiple lines and include additional clarifications.
+- **FEATURE** — name of the folder where the verification report will be saved. Taken from the value between the first two `#` symbols (e.g., `#payments#` → `payments`).
+- **CONTEXT** — main context and verification purpose. Consider everything after the second `#` in the parameter line; context can span multiple lines and include additional clarifications.
 
 **General rules**
 
@@ -77,4 +77,4 @@ Template helps format the results of automatic task execution verification and m
   - ❌ — not completed
   - ⚠️ — partially completed
 
-Write strictly in Markdown and add nothing outside the document. **Goal** — verify all tasks in `spec/features/{FEATURE}/tasks.md`, mark completed ones in the task file, create a detailed report `verify-report.md` with logs of all tasks and their statuses, or recommend moving the feature to `spec/archived/{FEATURE}` if all tasks passed.
+Write strictly in Markdown and add nothing outside the document. **Goal** — verify all tasks in `spec/features/{FEATURE}/tasks.md`, mark completed ones in the task file, create a detailed report `verify-report.md` with logs of all tasks and their statuses, or recommend moving the feature to `spec/archived/{FEATURE}` if all tasks passed.

package/spec/feature.md

@@ -4,10 +4,10 @@ Template allows creating a complete set of feature documents in one request duri
 
 **Parameters**
 
-- **FEATURE** — name of the folder where artifacts will be saved. Determined by the value between the first two `@` symbols (e.g., `@payments@` → `payments`).
-- **CONTEXT** — detailed feature description: goals, functional and non-functional requirements, constraints, implementation plan. Consider everything after the second `@` in the parameter line; text can span multiple lines and include lists.
+- **FEATURE** — name of the folder where artifacts will be saved. Determined by the value between the first two `#` symbols (e.g., `#payments#` → `payments`).
+- **CONTEXT** — detailed feature description: goals, functional and non-functional requirements, constraints, implementation plan. Consider everything after the second `#` in the parameter line; text can span multiple lines and include lists.
 
-Parameters are passed in one line in the format `@<feature>@ <context>` without XML-like tags.
+Parameters are passed in one line in the format `#<feature># <context>` without XML-like tags.
 
 **General rules**
 
@@ -37,4 +37,4 @@ The process should automatically create/update the following files:
 
 Each document should be created with complete content based on the templates from `spec/core/` and the provided **CONTEXT**.
 
-Write strictly in Markdown and automatically create/update the three documents. **Goal** — create a complete set of feature materials (what we do, how we implement, and what tasks we perform) in one request based on **CONTEXT**, with automatic file creation and directory structure management.
+Write strictly in Markdown and automatically create/update the three documents. **Goal** — create a complete set of feature materials (what we do, how we implement, and what tasks we perform) in one request based on **CONTEXT**, with automatic file creation and directory structure management.