thachvd-kit 1.0.25 → 1.0.27

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "thachvd-kit",
-    "version": "1.0.25",
+    "version": "1.0.27",
     "description": "Cross-agent project rules bootstrap kit for Codex, Antigravity, and Claude Code",
     "bin": {
         "thachvd-kit": "./bin/cli.js"
@@ -23,6 +23,8 @@
     },
     "scripts": {
         "test": "node test/cli.test.js",
+        "release:verify": "npm test && node --check bin/cli.js && npm pack --dry-run",
+        "preversion": "npm run release:verify",
         "release:patch": "npm version patch",
         "release:dry-run": "npm pack --dry-run",
         "release:publish": "npm publish"

package/workflows/release.md

@@ -0,0 +1,42 @@
+---
+description: Release the thachvd-kit npm package with verification, versioning, tagging, publishing, and registry checks.
+---
+
+# /release - Npm Release
+
+Use this workflow only after the implementation workflow is complete and the release commit is the only intended change.
+
+## Release Gate
+
+- [ ] Working tree is clean before starting.
+- [ ] Change is already reviewed and pushed to `main`.
+- [ ] `npm run release:verify` passes.
+- [ ] The next version is correct and has not been published.
+- [ ] npm authentication is available with `npm whoami`.
+- [ ] Rollback/response plan is known: npm versions cannot be overwritten or reused.
+
+## Commands
+
+```bash
+git status --short --branch
+npm run release:verify
+npm run release:patch
+git push origin main --follow-tags
+npm whoami
+npm run release:publish
+npm view thachvd-kit version
+npx thachvd-kit@<published-version> --help
+```
+
+`npm run release:patch` runs `preversion`, which executes the release verification, then `npm version patch` updates the package metadata and creates the version commit/tag. Do not run `npm publish` until the version and dry-run contents are correct.
+
+## Version Rules
+
+- Patch: backward-compatible fixes, docs, tests, and internal workflow improvements.
+- Minor: backward-compatible new CLI behavior or user-facing capability.
+- Major: breaking CLI, configuration, package, or generated-artifact contract.
+- Beta/prerelease: publish with a non-`latest` dist-tag, for example `npm publish --tag beta`.
+
+## Bypass Rules
+
+Questions and simple fixes bypass Spec/Plan/Review only when they do not change behavior or a shared contract. Publishing never bypasses `release:verify`, versioning, tagging, authentication, or registry verification.

package/workflows/simple.md

@@ -0,0 +1,40 @@
+---
+description: Fast path for one-file, unambiguous fixes with no behavior or shared-contract change.
+---
+
+# /simple - Fast Path
+
+$ARGUMENTS
+
+## Use Only When
+
+- The change is limited to one obvious file or one tiny local edit.
+- The expected result is unambiguous.
+- No behavior, API, schema, security, CI, dependency, workflow, or release contract changes.
+
+## Explicit Bypass
+
+Start the response with:
+
+```text
+FAST_PATH: simple-fix
+REASON: [why Spec/Plan/Review are not needed]
+SCOPE: [file or narrow area]
+```
+
+## Steps
+
+1. Inspect the target and its immediate context.
+2. Make the smallest change.
+3. Run focused verification.
+4. Report the changed file and evidence.
+
+Do not create a spec or plan for this route. Do not skip verification. If the scope expands, stop and re-route through `/task` as a feature, bug, or multi-domain task.
+
+## Examples
+
+```text
+/simple fix a typo in README.md
+/simple update one stale command in a workflow doc
+/simple change one test assertion message
+```

package/workflows/task.md

@@ -0,0 +1,57 @@
+---
+description: Route every task to the smallest safe workflow, fast path, bug flow, feature flow, or release flow.
+---
+
+# /task - Task Router
+
+$ARGUMENTS
+
+## Purpose
+
+Use `/task` at the start of a task when you are unsure which workflow, skill, or specialist agent applies. This command routes the request before implementation.
+
+## Required Output
+
+```text
+ROUTE: question | simple | feature | bug | review | release | multi-domain
+WORKFLOW: [exact .agent/workflows/<name>.md file]
+SKILLS: [skills to load, or none]
+AGENTS: [specialist agents to load, or none]
+GATE: fast-path | standard
+NEXT: [the next command or action]
+```
+
+Do not write code while routing. Ask one concise clarification question if the route cannot be determined safely.
+
+## Routing Rules
+
+| Signal | Route | Next action |
+|---|---|---|
+| Asking for information or architecture explanation | question | Answer directly; no edits |
+| One obvious file, no behavior or contract change | simple | Use `/simple <request>` |
+| New behavior, multiple files, unclear scope, or >30 minutes | feature | `/brainstorm` -> `/spec` when needed -> `/plan`, then approval |
+| Failing test, regression, error, or unknown root cause | bug | Use `/debug <symptom>` |
+| Review request or pre-merge check | review | Use `/review` |
+| npm version/tag/publish request | release | Use `/release` |
+| Several specialist domains | multi-domain | Use `/orchestrate` |
+
+## Workflow And Skill Map
+
+- `/simple`: `$clean-code` + `$verification-before-completion`.
+- `/brainstorm`: `brainstorming`; no code.
+- `/spec`: `.agent/workflows/spec.md`; define scope and acceptance criteria, no code.
+- `/plan`: `project-planner` + `plan-writing`; no code before approval.
+- `/enhance` or `/create`: relevant domain agent and implementation skills after approval.
+- `/debug`: `debugger` + `$systematic-debugging` + `testing-patterns`.
+- `/test`: `test-engineer` + `testing-patterns`.
+- `/review`: `$code-review-checklist` + `$verification-before-completion`.
+- `/release`: `release.md` and the npm release scripts; never use the fast path.
+
+## Examples
+
+```text
+/task add an export button
+/task login returns 500
+/task fix typo in README
+/task publish a new npm version
+```