architext 0.0.4 → 0.0.6

package/dist/templates/en/docs/prompts/edit.md

@@ -1,96 +1,106 @@
 <protocol_edit>
-  **Trigger**: `/archi.edit <id> [context]`
-  **Goal**: Based on new requirements/feedback, update Spec/UI docs of an already managed module and append development plans.
+  **Trigger**: `/archi.edit <id> [context]` | Auto-loaded by Workflow Dispatch on natural language trigger
+  **Goal**: Update managed module's Spec/UI docs per new requirements/feedback, and append development plan.
 
 <meta>
     <style>Collaborative, Iterative, Traceable</style>
     <language>English</language>
     <principles>
-      1.  **Doc First**: Must modify docs (Spec/UI) first, then generate Plan. Prohibited from skipping docs to change code plans directly.
-      2.  **Incremental**: Only append new Tasks to Plan, keep completed history (unless rollback needed).
+      1.  **Doc First**: Must modify docs (Spec/UI) first, then generate Plan. Do not skip docs to change code plan.
+      2.  **Incremental**: Only append new Tasks to Plan; keep completed history (unless rollback needed).
       3.  **Conflict Check**: Check if new requirements conflict with tech_stack / design_tokens.
-      4.  **Frontmatter Preservation**: Prohibited from destroying existing document Metadata.
+      4.  **Frontmatter Preservation**: Do not break existing document Metadata.
+      5.  **IDE-Native First**: Leverage IDE native capabilities to drive execution rhythm; this protocol defines quality standards and checkpoints, not fight IDE planning/execution mechanisms.
     </principles>
 </meta>
 
 <step_1_load>
-    **Role**: Product Manager
     **Action**:
-    - Read `[[__DOCS_DIR__]]/tasks/<ID>_<Slug>/` spec.md, ui.md, plan.json.
-    - [?UI] Read `[[__DOCS_DIR__]]/global/ui_context.md` (locate the screen scope and navigation graph for this task).
-    - Check `Spec-Status` field in spec.md:
-      - `Full` → Normal flow, proceed to step_2.
-      - `Stub` → Proceed to step_1_5_enrich.
-    - [?Major UX Change] Quick search for similar product best practices.
+    - Read spec.md, ui.md, plan.json under `[[__DOCS_DIR__]]/tasks/<ID>_<Slug>/`.
+    - (UI projects only) Read ui_context.md (locate screen scope and navigation for this feature).
+    - Check `Spec-Status` in spec.md: `Full` → normal flow step_2 | `Stub` → step_1_5_enrich.
+    - (Major UX change) Quick search for similar product best practices.
 </step_1_load>
 
 <step_1_5_enrich>
-    **Role**: Reverse Engineer
-    **Trigger**: spec.md contains `Spec-Status: Stub` (lightweight snapshot generated by `/archi.inherit`).
+    **Trigger**: spec.md contains `Spec-Status: Stub` (lightweight snapshot from `/archi.inherit`).
 
     **Action**:
-    1. Inform user: "This task only has a lightweight snapshot. A full spec must be generated before modifications can proceed."
-    2. Extract source file paths from the stub's "Associated Files" section.
-    3. Read each associated file with medium-depth scan (entry point + core logic).
-    4. Enrich the stub into a full spec based on code analysis:
-       - Preserve existing overview and key flows
-       - Add Gherkin Scenarios (covering normal flows + exception paths)
-       - Add interface/type definitions (if this task is upstream of others)
-    5. Update `Spec-Status: Stub → Full`.
-    6. [?UI] If module has UI → generate or update `ui.md` (scope declaration); if new screens are needed, [[SKILL: archi-ui-wireframe|invoke skill or notify user to run]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md` and prompt user to follow the document)]] (Skill syncs both `ui_concept.html` + `ui_context.md`).
-    7. Generate `plan.json` (all tasks as done, recording implemented content).
-    8. Present enriched spec summary to user.
-
-    **Gate**: User confirms enriched content is correct before proceeding to step_2_refine_docs.
+    1. Inform user: "This task has only a lightweight snapshot; must complete full spec before modification."
+    2. Extract source paths from stub "Associated Files"; read each (entry + core logic).
+    3. Enrich into full spec from code analysis: keep existing overview and flows; add Gherkin Scenarios + interface/type definitions.
+    4. Update `Spec-Status: Stub → Full`.
+    5. (UI projects only) If module has UI → generate `ui.md`; if new screens needed, [[SKILL: archi-ui-wireframe|invoke skill]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md`)]].
+    6. Generate `plan.json` (all tasks done).
+    7. Output enriched spec summary to user.
+
+    **Gate**: Proceed to step_2_refine_docs after user confirms.
     **Exception**: Associated files missing/moved → prompt user to update paths.
 </step_1_5_enrich>
 
 <step_2_refine_docs>
-    **Role**: Requirements Analyst & Designer
     **Action**:
-    - Modify spec.md (logic/rule changes) and ui.md (structure/interaction changes) based on `[context]`.
-    - [?UI Modification] [[SKILL: archi-ui-wireframe|Follow the skill protocol to sync `ui_concept.html` + `ui_context.md` (Skill is the sole writer of both files)]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md` and follow its protocol)]]:
+    - Modify spec.md and ui.md per `[context]`.
+    - (UI modified) [[SKILL: archi-ui-wireframe|Follow the skill protocol to sync `screens/S-XX.html` + `ui_context.md`]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-ui-wireframe/SKILL.md`)]]:
 
-      | Change Type | Criteria | Action |
+      | Change Type | Criteria | Handling |
       |:---|:---|:---|
-      | No screen impact | Logic/data only, no visual diff | Update spec.md only; `ui_concept.html` / `ui_context.md` unchanged |
-      | Minor UI tweak | New/modified state, popup, or local area; overall layout unchanged | Call skill (Modify screens mode) to update both files; output `MODIFIED: S-XX` |
-      | Screen structure change | Layout refactor, new standalone screen, navigation path change | Call skill (Modify screens mode) to update both files; output `MODIFIED: S-XX`; if Phase 2 coloring is done, re-color only the modified screen |
-      | Task reduction | Screen/region removed entirely | Call skill (Remove screens mode) to update both files; output `REMOVED: S-XX` |
+      | No screen impact | Logic/data change only | Update spec.md only |
+      | Minor UI tweak | New/modified state, popup, local area | Call skill to update; output `MODIFIED: screens/S-XX.html` |
+      | Screen structure change | Layout refactor, new screen, navigation change | Call skill to update |
+      | Task reduction | Screen/region removed entirely | Call skill to remove; output `REMOVED: screens/S-XX.html` |
 
-    - Ask user questions (A/B/C/D options) to confirm details when requirements are vague.
+    - Ask user when requirements are vague.
 
-    **Output**: Updated Spec, UI documents, and `ui_concept.html` / `ui_context.md` change summary.
+    **Output**: Updated docs and change summary.
 </step_2_refine_docs>
 
 <step_3_update_plan>
-    **Role**: Tech Lead
     **Action**:
-    - Append new Phase object to `plan.json` phases array.
-    - List specific Tasks (API update, UI tweak, Test update); each must be verifiable.
-    - **Status Transition**: If current task status=`done`, reset to `active` after appending the Phase (otherwise `/archi.code` will be rejected by the Status Gate).
+    - Append new Phase to `plan.json` with specific Tasks; each must be verifiable.
+    - **Status transition**: When status=`done`, after appending Phase must reset to `active`.
 
-    **Terminal Gate** (Do not skip; must complete before step_3_5 starts):
+    **Terminal Gate** (do not skip): Standard check (task --check + render).
     | Step | Command | Pass Condition |
     |:---|:---|:---|
-    | 1 | `npx archi task --check` | No ERROR-level issues |
-    | 2 | `npx archi render` | `.md` views generated |
-    | 3 | [if current status=done] `npx archi task <ID> --status active` | Task status reset to active |
+    | 3 | [when status=done] `npx archi task <ID> --status active` | Status reset |
 
-    **Output**: plan.json with new tasks appended; if status transition was performed, output `MODIFIED: roadmap.json <ID>.status done→active`.
+    **Output**: plan.json with new tasks appended; if status transition performed, output `MODIFIED: roadmap.json <ID>.status done→active`. Enter step_4_data_sync.
 </step_3_update_plan>
 
-<step_3_5_verify>
+<step_4_data_sync>
+    **Data governance sync**:
+
+    [[SUBAGENT: archi-data-sync|context: Scan new business entities/error codes/Schema/endpoints/commands/exports from requirement changes, incrementally sync per 00_system.md]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-data-sync/SKILL.md`, follow its execution protocol)]]
+</step_4_data_sync>
+
+<step_4_verify>
     **Role**: Independent Reviewer
 
-    [[SUBAGENT: archi-silent-audit|mode: plan-docs, context: Review step_2 updated spec.md/ui.md and step_3 appended plan.json new Phase; ensure doc logic is consistent and new Phase tasks are verifiable]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-silent-audit/SKILL.md`, follow mode: plan-docs review dimension table item by item)]]
+    [[SUBAGENT: archi-silent-audit|mode: plan-docs, context: Review step_2 updated spec.md/ui.md and step_3 appended plan.json new Phase]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-silent-audit/SKILL.md`, follow mode: plan-docs review)]]
 
     [[INCLUDE: shared/verify-result-handling.md]]
-</step_3_5_verify>
+</step_4_verify>
+
+<step_6_summary>
+    **Pre-signoff Checklist** (confirm each item before Output):
+    □ spec.md — updated per context, changes tracked
+    □ (if UI changed) ui.md + screens/S-XX.html + ui_context.md — synced
+    □ plan.json — new Phase appended (history tasks fully preserved)
+    □ (if original status=done) roadmap.json — status reset to active
+    □ Global files — related JSON files synced for changes:
+      - dictionary.json + error_codes.json + env_registry.json — required
+      - (UI projects only) design_tokens.json + ui_context.md
+      - (Data projects only) data_snapshot.json
+      - (API projects only) api_snapshot.json
+      - (CLI projects only) command_api.json
+      - (Lib projects only) public_api.json
+    □ Step 4 Data Sync — archi-data-sync executed
+    □ Step 4 Silent Audit — executed, all CRITICAL issues resolved
+    □ Terminal Gate — task --check no ERROR (executed in step_3)
 
-<step_4_summary>
     **Action** (Gate must complete in step_3):
     **Output**: Task update summary with Spec/UI/Plan change overview and Next Steps table. Recommend running `/archi.code <ID>`.
-</step_4_summary>
+</step_6_summary>
 
 </protocol_edit>

package/dist/templates/en/docs/prompts/fix.md

@@ -1,86 +1,102 @@
 <protocol_fix>
-  **Trigger**: `/archi.fix [id] <context>`
-  **Goal**: Diagnose Bug and execute fix directly. If `[id]` not provided, auto-locate relevant task module.
+  **Trigger**: `/archi.fix [id] <context>` | Auto-loaded by Workflow Dispatch on natural language trigger
+  **Goal**: Diagnose and fix bugs. If `[id]` not provided, auto-locate related feature module by context.
 
 <meta>
     <style>Diagnostic, Surgical, Spec-Compliant</style>
     <language>English</language>
     <principles>
-      1.  **Spec Immutable**: Prohibited from modifying `spec.md` / `ui.md` (unless Bug itself is a documentation error).
-      2.  **Reproduction**: Must conceive reproduction steps or test cases first.
-      3.  **Root Cause**: Must analyze root cause, not patch the surface.
+      1.  **Spec Immutable**: Do not modify `spec.md` / `ui.md` (unless the bug is a doc error).
+      2.  **Reproduction**: Must have reproduction steps or test case first.
+      3.  **Root Cause**: Must analyze root cause, not patch surface.
       4.  **Test-Driven**: Fix plan must include new test cases.
-      5.  **Auto-Discovery**: If ID not specified, locate Task via Context semantic search.
+      5.  **Auto-Discovery**: If ID not specified, locate Task via context semantic search.
+      6.  **IDE-Native First**: Leverage IDE native capabilities to drive execution rhythm; this protocol defines quality standards and checkpoints, not fight IDE planning/execution mechanisms.
     </principles>
 </meta>
 
 <step_1_diagnose>
-    **Role**: Fault Analyst
+    **Role**: Failure Analyst
     **Action**:
     1.  **Resolve Target**:
-        - Has `<id>`: Lock target `tasks/<ID>_<Slug>/`.
-        - No `<id>`: Analyze `[context]` to search most relevant module.
-          Unique match → Auto lock | Multiple matches → List candidates and ask | Cannot locate → Report error requesting ID.
-    2.  Read all docs under target directory (`spec.md`, `ui.md`, `plan.json`) and related code.
-    3.  Read `02_tech_stack.md` (ensure fix does not violate tech red lines) and `[[__DOCS_DIR__]]/global/vision.md` (ensure fix direction stays aligned with project vision).
-    4.  Analyze `[context]`, combine with code logic to locate potential failure points.
-    5.  **Hypothesis**: Propose 1-3 root cause hypotheses.
-
-    **Output**: Root Cause Analysis report.
+        - With `<id>`: Lock `tasks/<ID>_<Slug>/`.
+        - Without `<id>`: Analyze `[context]` to find most relevant module.
+          Single match → auto lock | Multiple matches → list candidates and ask | Cannot locate → error, request ID.
+    2.  Read all docs and related code in target directory.
+    3.  Read tech_stack.md (tech red lines) and vision.md (direction anchor).
+    4.  Analyze `[context]` with code logic to locate potential fault points.
+    5.  **Hypothesis**: Propose 1–3 root cause hypotheses.
+
+    **Output**: Fault diagnosis report (Root Cause Analysis).
 </step_1_diagnose>
 
 <step_2_plan_fix>
-    **Role**: Tech Lead
     **Action**:
-    - Update `[[__DOCS_DIR__]]/tasks/<ID>_<Slug>/plan.json`, append to `phases` array a phase object with `name`: `Bugfix: <Bug Title>`.
-    - Tasks: 1) Create reproduction test (Red) 2) Apply fix (Green) 3) Regression test.
+    - Update plan.json; append phase `Bugfix: <Bug Title>`.
+    - Tasks: 1) Create reproduction test (Red) 2) Fix (Green) 3) Regression test.
 
-    **Terminal Gate** (Do not skip; must complete before step_5 output):
-    | Step | Command | Pass Condition |
-    |:---|:---|:---|
-    | 1 | `npx archi render` | `.md` views generated |
+    **Terminal Gate** (do not skip): Standard check (task --check + render).
 
     **Output**: plan.json with fix tasks appended.
 </step_2_plan_fix>
 
 <step_3_execute_fix>
-    **Role**: Senior Engineer (Surgical Fix — bug only, no scope creep)
     **Action**:
-    - Modify code directly according to Plan.
-    - Fix Bug only; prohibited from opportunistic refactoring or modifying unrelated code.
-    - Error handling follows `code.md` specs (no swallowing errors/no silent failures).
+    - Modify code per Plan. Fix bug only; do not refactor.
+    - Error handling follows `code.md` protocol.
 </step_3_execute_fix>
 
 <step_4_verify>
-    **Role**: QA Engineer
-    **Terminal Gate** (Do not skip; must complete before step_5 output):
+    **Terminal Gate** (do not skip):
     | Step | Command | Pass Condition |
     |:---|:---|:---|
-    | 1 | Run build command | Build succeeds |
+    | 0 | Check `scripts/validate` | If exists, must run; results per script |
+    | 1 | Run build command | Build success |
     | 2 | Run type check | Zero type errors |
     | 3 | Run Lint/Format | Pass |
-    | 4 | Run tests | Reproduction + regression tests pass |
+    | 4 | Run tests | Reproduction test + regression test pass |
+
+    Fix any failure until pass.
 
-    Any failure must be fixed until passed.
+    **Code quality review**:
+    [[SUBAGENT: archi-silent-audit|mode: code-impl, context: Review fix code; focus Tech/Security/Performance + Spec Immutable]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-silent-audit/SKILL.md`, follow mode: code-impl check)]]
+
+    [[INCLUDE: shared/verify-result-handling.md]]
 </step_4_verify>
 
-<step_4_5_plan_update>
-    **Role**: Tech Lead
+<step_4_5_data_sync>
+    **Data governance sync**:
+
+    [[SUBAGENT: archi-data-sync|context: Scan new business entities/error codes/Schema from Bug fix, incrementally sync per 00_system.md]][[NO-SKILL: (Skill not installed: read `[[__DOCS_DIR__]]/skills/archi-data-sync/SKILL.md`, follow its execution protocol)]]
+</step_4_5_data_sync>
+
+<step_5_plan_update>
     **Action**:
-    1. Update `plan.json`: set `done: true` for completed tasks in the Bugfix Phase.
-    2. [current status=`done` and all Bugfix Phase tasks passed] → Keep status as `done`.
-    3. [Bugfix Phase has unresolved tasks] → Run `npx archi task <ID> --status active`; note in signoff that `/archi.code` is needed to complete remaining fixes.
+    1. Update plan.json Bugfix Phase completed tasks `done: true`.
+    2. [status=`done` and Bugfix all pass] → keep `done`.
+    3. [Bugfix has incomplete items] → `npx archi task <ID> --status active`; signoff note to re-run `/archi.code`.
+
+    **Output**: `MODIFIED: plan.json Bugfix Phase done flags`. Enter step_6_summary.
+</step_5_plan_update>
 
-    **Output**: `MODIFIED: plan.json Bugfix Phase done marks` (if status changed, append `MODIFIED: roadmap.json <ID>.status`).
-</step_4_5_plan_update>
+<step_6_summary>
+    **Pre-signoff Checklist** (confirm each item before Output):
+    □ Root cause analyzed (not surface patch), Hypothesis output in step_1
+    □ plan.json — Bugfix Phase appended (step_2)
+    □ Reproduction test created and verified (Red → Green)
+    □ Code fix targets Bug only, no opportunistic refactoring
+    □ Step 4.5 Data Sync — archi-data-sync executed
+    □ Step 4 Terminal Gate — Build / type check / Lint / tests all passed
+    □ Step 4 Silent Audit — executed, all CRITICAL issues resolved
+    □ plan.json Bugfix Phase — done flags updated (step_5)
 
-<step_5_summary>
     **Output**: Bug fix summary with Root Cause analysis, fix content, new tests, and Next Steps table:
 
     | Priority | Action | Notes |
     |:---|:---|:---|
-    | Recommended | `/archi.audit <ID>` | Re-audit to confirm fix is complete and no new issues introduced |
-    | Optional | `/archi.code <ID>` | If Bugfix Phase has remaining incomplete tasks |
-</step_5_summary>
+    | (If no scripts/) | `/archi.script` | Generate automation validation scripts |
+    | Recommended | `/archi.audit <ID>` | Re-audit to confirm fix complete |
+    | Optional | `/archi.code <ID>` | If incomplete items, continue implementation |
+</step_6_summary>
 
 </protocol_fix>

package/dist/templates/en/docs/prompts/help.md

@@ -1,69 +1,61 @@
 <protocol_help>
   **Trigger**: `/archi.help [question]`
-  **Goal**: Project navigation and contextual Q&A. Analyze current project state to recommend next actions; or answer user questions based on project context.
+  **Goal**: Project navigation and context Q&A. Analyze project current state, recommend next actions; or answer user questions based on project context.
 
 <meta>
     <style>Concise, Contextual, Actionable</style>
     <language>English</language>
     <principles>
-      1.  **Context-Aware**: Answer based on real project state. No guessing.
-      2.  **Actionable Output**: Every output must include an executable next step (specific command + args).
-      3.  **Minimal Token**: Keep output concise. Don't repeat what the user already knows. Only present conclusions and recommendations.
-      4.  **No Audit**: No deep auditing (that's `/archi.audit`'s job). Focus on navigation and Q&A.
+      1.  **Context-Aware**: Answer based on actual project state; no guessing.
+      2.  **Actionable Output**: Every output must include executable next-step suggestions (concrete command + params).
+      3.  **Minimal Token**: Concise output; don't restate known info. Present reasoning and suggestions only.
+      4.  **No Audit**: Do not do deep audit (that's `/archi.audit`). Focus on navigation and Q&A.
     </principles>
 </meta>
 
 <step_1_load_context>
-    **Role**: Project Observer
     **Action**:
-    1.  Read `[[__DOCS_DIR__]]/global/roadmap.json` — extract only `id/title/status/deps/tag` fields per task; skip `goal/notes` (navigation and status aggregation do not need these details).
-    2.  Scan `[[__DOCS_DIR__]]/tasks/` directory — get existing Tasks and their doc completeness (spec.md / ui.md / plan.json).
-    3.  [?question] If user provided a question, locate relevant files by semantic match (spec / plan / vision / tech_stack / data_snapshot, etc.), read as needed.
+    1.  **Load**: roadmap.json (id/title/status/deps/tag only; skip goal/notes).
+    2.  **Scan Tasks**: Scan tasks/ — get existing Tasks and doc completeness (has spec.md / ui.md / plan.json).
+    3.  [?question] If user provided a question, locate and read relevant files by semantics.
 
     **Output**: Internal context (not shown to user).
 </step_1_load_context>
 
 <step_2_route>
-    **Role**: Router
-    **Action**: Branch based on input:
+    **Action**: Branch by input:
 
     | Input | Branch |
     |:---|:---|
     | No args | → step_3_navigate (project navigation) |
-    | Has `[question]` | → step_4_answer (contextual Q&A) |
+    | Has `[question]` | → step_4_answer (context Q&A) |
 
 </step_2_route>
 
 <step_3_navigate>
-    **Role**: Project Navigator
     **Action**:
     1.  **Determine project phase**:
 
-        | Signal | Phase | Recommendation |
+        | Signal | Phase | Suggestion |
         |:---|:---|:---|
         | roadmap.json missing | Not initialized | New project → `/archi.start`; existing code → `/archi.inherit` |
-        | Has roadmap but no Task dirs | Started, not planned | Run `/archi.scope` to plan new tasks |
-        | Has Legacy stubs (Spec-Status: Stub) | Inherited, not enriched | Run `/archi.edit LEG-xx` to enrich spec |
-        | Has active tasks with complete plan.json | Ready to code | Run `/archi.code <ID>` |
-        | Has active tasks but missing spec/plan | Planning incomplete | Run `/archi.plan <ID>` to complete |
-        | All tasks done | Complete | Run `/archi.scope` to plan new tasks or release |
-        | Has blocked tasks | Blocked | Show blocking reason and prerequisites |
-
-    2.  **Output format**:
-        - One-line summary of current state
-        - Recommended next action (with specific command)
-        - If multiple paths available, list by priority (max 3)
+        | Has roadmap but no tasks/ | Started, not planned | `/archi.scope` to plan new tasks |
+        | Has Legacy stub (Spec-Status: Stub) | Inherited, not enriched | `/archi.edit LEG-xx` to enrich spec |
+        | Has active task and plan.json complete | Ready to code | `/archi.code <ID>` |
+        | Has active task but missing spec/plan | Planning incomplete | `/archi.plan <ID>` to complete |
+        | All tasks done | Completed | `/archi.scope` to plan new or release |
+        | Has blocked task | Blocked | Show block reason and upstream deps |
+
+    2.  **Output**: One-line state summary + recommended next step (with command) + optional paths (≤3, by priority).
 </step_3_navigate>
 
 <step_4_answer>
-    **Role**: Project Advisor
     **Action**:
-    1.  Parse `[question]` semantics, locate relevant project files.
-    2.  Read relevant files, synthesize answer.
-    3.  If question involves an action (e.g. "how to do X"), include specific command suggestions.
-    4.  If insufficient info to answer, state what's missing instead of fabricating.
+    1.  Parse `[question]` semantics; locate and read relevant project files.
+    2.  Answer comprehensively; operational questions must include concrete command suggestions.
+    3.  When info insufficient, state what's missing; do not fabricate.
 
-    **Output**: Concise answer based on project context + relevant file references.
+    **Output**: Concise answer based on project context + relevant file refs.
 </step_4_answer>
 
 </protocol_help>