@uocnv1998/agent-kit 1.0.1 → 1.0.2

package/bin/index.js

@@ -128,7 +128,7 @@ try {
             console.log(`\n\n${colors.pipe} Initializing OpenSpec for the project...`);
             // Only run init if openspec directory doesn't exist to avoid errors
             if (!fs.existsSync(path.join(currentDir, 'openspec'))) {
-                execSync('openspec init', { stdio: 'inherit', cwd: currentDir });
+                execSync('openspec init --tools antigravity --force', { stdio: 'inherit', cwd: currentDir });
             }
 
             // Automatically configure OpenSpec to generate artifacts in Vietnamese
@@ -143,7 +143,7 @@ try {
                 }
             }
 
-            execSync('openspec update', { stdio: 'inherit', cwd: currentDir });
+            execSync('openspec update --force', { stdio: 'inherit', cwd: currentDir });
             console.log(`${colors.pipe} OpenSpec structure created/updated`);
         } catch (specError) {
             console.error(`\n${colors.cross} OpenSpec setup failed. You may need 'sudo' permissions on Mac/Linux.`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uocnv1998/agent-kit",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "CLI tool to scaffold Agent Skills, Rules, and Workflows",
   "main": "bin/index.js",
   "bin": {

package/templates/.agent/dev/backend/rules/GEMINI.md

@@ -78,9 +78,10 @@ When applying the agent, inform the user:
 ### 🌐 Core Development Principles (MANDATORY)
 
 - **SOLID Principles**: Controllers must stay thin and call services, services contain business logic and depend only on repository interfaces, and all database access must be handled exclusively inside repository implementations via dependency injection.
-- **TDD (Test-Driven Development)**: Always write tests BEFORE writing the implementation. Run tests frequently and ensure the test coverage rate is greater than 80%.
-- **Clean Code**: Run `vendor/bin/pint --dirty --format agent` before finalizing changes.
+- **TDD (Test-Driven Development)**: Always write tests BEFORE writing the implementation. You must write both unit tests and feature tests. Run tests frequently and ensure the overall project test coverage rate is 80% or higher.
+- **Clean Code**: Run the appropriate code formatter based on the project's language and framework before finalizing changes. The specific formatting command may be defined in `AGENTS.md`.
 - **Security**: Use environment variables only in configuration files - never use `env()` directly outside of config files.
+- **OpenSpec & TDD Integration**: Whenever executing OpenSpec workflows (e.g., `/opsx:propose`, `/opsx:apply`), you MUST enforce TDD. During `/opsx:propose`, the `tasks.md` MUST explicitly break down features into `[ ] Write failing test (RED)`, `[ ] Implement (GREEN)`, and `[ ] Refactor`. During `/opsx:apply`, you are FORBIDDEN from writing implementation code before passing tests are demonstrated.
 
 ### 🌐 Documents (Workspace files)
 

package/templates/.agent/dev/common/workflows/dev-workflow.md

@@ -19,12 +19,16 @@ When receiving a task (via Jira Ticket or direct prompt), you must act as if the
   1. `proposal.md` - Why we're doing this, what's changing.
   2. `specs/` - Requirements and scenarios.
   3. `design.md` - Technical approach.
-  4. `tasks.md` - Implementation checklist.
+  4. `tasks.md` - Implementation checklist. **CRITICAL TDD REQUIREMENT: Each logical feature MUST be broken down into strict TDD steps in the checklist: `[ ] Write failing test (RED)`, `[ ] Implement minimum code to pass (GREEN)`, and `[ ] Refactor`.**
 - After generating these files, STOP and ask the user to review them via `/opsx:apply`.
 
-### Phase 2: Implementation (Tiến hành Code)
+### Phase 2: Implementation (Tiến hành Code - TDD MANDATORY)
 - **Command**: `/opsx:apply`
 - When you receive this command, you will start implementing the code strictly following the checklist in `tasks.md`.
+- 🔴 **TDD REQUIREMENT (MANDATORY)**: You MUST follow the **TDD Workflow (RED-GREEN-REFACTOR)** for EVERY implementation task. You are FORBIDDEN from writing implementation code before tests.
+    1. **RED**: Write the failing test FIRST based on the spec/task.
+    2. **GREEN**: Write the minimal code to make the test pass.
+    3. **REFACTOR**: Improve the code while keeping tests green.
 - As you complete portions of the work, mark off items in the `tasks.md` internal memory.
 - **MANDATORY**: Upon completing the backend implementation, you MUST document the new or updated APIs:
     1. Create or update an API Specification page on **Confluence** (using `atlassian-mcp-server_createConfluencePage` or `updateConfluencePage`).

package/templates/.agent/dev/frontend/rules/GEMINI.md

@@ -83,6 +83,7 @@ When applying the agent, inform the user:
 - **Clean Code & Formatting**: Run `npm run lint` and `npm run format` (or equivalent) before finalizing changes. Ensure consistent naming (PascalCase for Components, camelCase for variables/functions).
 - **Accessibility (a11y)**: Semantic HTML is mandatory. Every interactive element must be keyboard-accessible and have appropriate ARIA attributes.
 - **Performance**: Minimize client-side JavaScript. Use Next.js Server Components by default. Optimize images and avoid unnecessary re-renders.
+- **OpenSpec & TDD Integration**: Whenever executing OpenSpec workflows (e.g., `/opsx:propose`, `/opsx:apply`), you MUST enforce TDD. During `/opsx:propose`, the `tasks.md` MUST explicitly break down features into `[ ] Write failing test (RED)`, `[ ] Implement (GREEN)`, and `[ ] Refactor`. During `/opsx:apply`, you are FORBIDDEN from writing implementation code before passing tests are demonstrated.
 
 ### 🌐 Documents (Workspace files)