ai-workflow-init 1.2.0 → 1.2.2

package/.cursor/commands/execute-plan.md

@@ -54,7 +54,13 @@ If creating implementation doc for first task:
   - `## Follow-ups` - TODOs or deferred work
 - Follow the template format strictly
 
-## Step 5: Next Actions
+## Step 5: Quality Checks
+After completing Step 4 for each task batch:
+- Run linting on changed files (e.g., `eslint` if JavaScript/TypeScript project).
+- Run type checks if applicable (e.g., `tsc --noEmit`).
+- Fix issues (up to 3 attempts) before proceeding to the next task.
+
+## Step 6: Next Actions
 After completing tasks:
 - Suggest running `code-review` to verify against standards
 - Suggest running `writing-test` if edge cases need coverage

package/.cursor/commands/generate-standards.md

@@ -61,12 +61,38 @@ Generate two documents (with template preload):
 - Test placement and naming conventions
 - Config/secrets handling summary
 
-## Step 4: Persist
-- Overwrite or create:
+## Step 4: Persist (Update-in-place, Non-destructive)
+- Target files:
   - `docs/ai/project/CODE_CONVENTIONS.md`
   - `docs/ai/project/PROJECT_STRUCTURE.md`
 - Add header note: "This document is auto-generated from codebase analysis + brief Q&A. Edit manually as needed."
-- If template files exist, ensure the generated `CODE_CONVENTIONS.md` starts with their merged content in the preload order above, then append auto-discovered rules.
+- Do NOT blindly overwrite entire files. Update only the managed blocks using markers:
+
+### Managed Block Markers
+Use these exact markers to wrap generated content:
+```
+<!-- GENERATED: CODE_CONVENTIONS:START -->
+... generated content ...
+<!-- GENERATED: CODE_CONVENTIONS:END -->
+```
+```
+<!-- GENERATED: PROJECT_STRUCTURE:START -->
+... generated content ...
+<!-- GENERATED: PROJECT_STRUCTURE:END -->
+```
+
+### Update Rules
+1) If the target file exists and contains the corresponding markers, replace only the content between START/END with the newly generated content.
+2) If the file exists but does not contain markers, append a new managed block to the end of the file (preserve all existing manual content).
+3) If the file does not exist, create it with the header note and a single managed block.
+4) Never modify content outside the managed blocks.
+
+### Generated Content Order (for CODE_CONVENTIONS)
+- Merge templates in preload order (when present):
+  1) `docs/ai/project/template-convention/common.md`
+  2) `docs/ai/project/template-convention/javascript.md` (when JS/TS repo)
+  3) `docs/ai/project/template-convention/react.md` (when React is detected)
+- After the merged templates, append auto-discovered rules from the codebase analysis.
 
 ## Step 5: Next Actions
 - Suggest running `code-review` to validate new standards are being followed

package/.cursor/commands/init-chat.md

@@ -0,0 +1,30 @@
+## Goal
+Initialize a new chat by loading and aligning to `AGENTS.md` so the AI agent consistently follows project rules (workflow, tooling, communication, language mirroring) from the first message.
+
+## What this command does
+1. Read `AGENTS.md` and extract the actionable rules.
+2. Summarize responsibilities and constraints the agent must follow in this session.
+3. Confirm language-mirroring: respond in the user's chat language; default to English if the user's language is unclear or ambiguous.
+4. Acknowledge the 4-phase workflow and TODO discipline for future commands.
+
+## Steps
+1) Open and read `AGENTS.md` (project root).
+2) Detect project languages/frameworks/libraries from repository metadata (e.g., `package.json`, `pyproject.toml`, lockfiles, config files). Update `docs/ai/project/CODE_CONVENTIONS.md` to include any missing key coding conventions (only important items like React, TypeScript, TailwindCSS, etc.).
+3) Read files in `docs/ai/project/` to understand project context and standards.
+4) Produce a short confirmation in the chat including:
+   - Workflow alignment: Plan → Implement → Test → Review
+   - Tooling strategy: semantic search first; parallelize independent steps
+   - Communication: minimal Markdown; status updates; high-signal summaries; mirror user language (default English if unclear)
+   - Code presentation: code references for existing code; fenced blocks for new code
+   - TODO policy: create/update todos; keep only one `in_progress`
+5) If any section is missing or unclear, ask a single concise clarification question; otherwise proceed silently in future commands.
+
+## Output format (concise)
+- Use the language of the triggering user message (mirror). If ambiguous, use English.
+- One short paragraph confirming alignment + a 4–6 bullet checklist of the above items.
+- No code unless strictly needed.
+
+## Notes
+- This command is idempotent—safe to re-run at the start of any chat.
+- It does not modify files; it only sets expectations for subsequent commands.
+

package/AGENTS.md

@@ -13,6 +13,7 @@
 ## Communication
 - Use Markdown only when necessary; use backticks for `files/dirs/functions/classes`.
 - Provide status updates before/after important actions; provide a high-signal summary at completion.
+- Mirror the user's chat language in responses (respond in the user's language); default to English if the user's language is unclear or ambiguous.
 
 ## Code presentation
 - Existing code: cite using a code reference block with `startLine:endLine:filepath` (no language tag).

package/docs/ai/implementation/feature-template.md

@@ -1,5 +1,7 @@
 # Implementation Notes: {Feature Name}
 
+Note: All content in this document must be written in English.
+
 ## Summary
 - Short description of the solution approach
 

package/docs/ai/planning/feature-template.md

@@ -1,5 +1,7 @@
 # Plan: {Feature Name}
 
+Note: All content in this document must be written in English.
+
 ## Goal
 - Objectives, scope, acceptance criteria (Given-When-Then)
 

package/docs/ai/testing/feature-template.md

@@ -1,5 +1,7 @@
 # Test Plan: {Feature Name}
 
+Note: All content in this document must be written in English.
+
 ## Test Files Created
 - `path/to/test-file.spec.js` - Tests for [component/function]
 - `path/to/another-test.spec.js` - Tests for [component/function]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-workflow-init",
-  "version": "1.2.0",
+  "version": "1.2.2",
   "description": "Initialize AI workflow docs & commands into any repo with one command",
   "bin": {
     "ai-workflow-init": "./cli.js"