spec-feature 1.0.2 → 1.0.3

package/README.md

@@ -1,6 +1,26 @@
 # SpecFeature
 
-SpecFeature is a sequential process for preparing and maintaining features: from formulating business context to verifying completed tasks. It helps synchronize product, engineering, and QA teams, reduce the number of "on-the-fly" changes, and establish success criteria before development begins. All artifacts are generated by LLM based on a single input context.
+SpecFeature helps you create feature specifications automatically. Just describe what you want to build, and it generates a complete specification, technical plan, and task list for your development team. All documents are created by AI from a single description.
+
+## Why use SpecFeature?
+
+### **Clearer starting point**
+The specification becomes the single source of truth — you guess less about what you intended to build.
+
+### **Fewer misunderstandings between human and AI**
+Clear "contracts" / specifications help avoid "vibe coding" — when AI "guesses" your intention and often builds something not quite what you need.
+
+### **Architecture and decisions are documented**
+"Why did we choose this solution?" will be captured in the specification / constitution, not in emails, chats, or someone's head.
+
+### **Controlled task breakdown**
+Small tasks are easier to review, test, and correct — fewer "big commits that are hard to understand".
+
+### **Flexibility and evolution**
+Specifications are not "dead" — they can be updated, refactored, and revised when requirements change.
+
+### **AI assistant integration**
+Specification + plan + tasks gives AI "context" and boundaries within which it can generate code more safely.
 
 ## Installation
 
@@ -85,37 +105,30 @@ npm install spec-feature
 
 ## Getting started
 
-To launch specification creation, use `spec/feature.md`. It will create a specification, plan, and task list in one request.
+To create a feature specification, use `spec/feature.md` template with any AI Assistant that can create folders and files (such as `Claude Code`, `Gemini CLI`, `Codex CLI`, `Copilot`, `Cursor`, etc.).
 
-**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.
-```
-
-This will create the `spec/features/user-auth/` folder with three files: `spec.md`, `plan.md`, and `tasks.md`.
-
-## Input parameter format
+### Input parameter format
 
 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.
 
-## How to launch specification creation
+### 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.
+```
+
+### What happens next
 
-Use any AI Assistant that can create folders and files, such as: `Claude Code`, `Gemini CLI`, `Codex CLI`, `Copilot`, `Cursor`, etc.
+The AI assistant generates three Markdown documents in sequence:
+- `spec/features/{FEATURE}/spec.md` — specification describing value and user scenarios.
+- `spec/features/{FEATURE}/plan.md` — technical plan based on specification and context.
+- `spec/features/{FEATURE}/tasks.md` — checklist of tasks for implementation and testing.
 
-1. **Pass it a prompt in this format**
-   ```
-   Use the template from spec/feature.md.
-   @<feature>@ <context>
-   ```
-2. **What happens next**
-   The AI assistant generates three Markdown documents in sequence:
-   - `spec/features/{FEATURE}/spec.md` — specification describing value and user scenarios.
-   - `spec/features/{FEATURE}/plan.md` — technical plan based on specification and context.
-   - `spec/features/{FEATURE}/tasks.md` — checklist of tasks for implementation and testing.
+For example, the above command will create the `spec/features/user-auth/` folder with three files: `spec.md`, `plan.md`, and `tasks.md`.
 
 ## How to launch task execution based on created specifications
 

package/package.json

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