@heyai-rules/pilo-masterkit 1.2.2 → 2.1.0

package/.agent/workflows/init-docs.md

@@ -1,46 +1,46 @@
----
-description: Tự động khởi tạo cấu trúc thư mục tài liệu cho dự án Pilo Masterkit.
----
-
-# Workflow: Khởi tạo Thư mục Tài liệu (Documentation Init)
-
-Quy trình này tự động tạo các thư mục cần thiết để quản lý tài liệu, báo cáo và nhiệm vụ theo chuẩn Pilo Masterkit.
-
-## Các bước thực hiện:
-
-1. **Kiểm tra và Tạo Thư mục**:
-   Tạo thư mục `docs/` ở thư mục gốc của dự án (nếu chưa có), sau đó tạo 8 thư mục con bên trong `docs/`:
-   - `docs/lessons/`: Lưu trữ bài học kinh nghiệm.
-   - `docs/reports/`: Lưu trữ báo cáo tiến độ và audit.
-   - `docs/plans/`: Lưu trữ kế hoạch triển khai.
-   - `docs/status/`: Lưu trữ trạng thái dự án.
-   - `docs/tasks/`: Lưu trữ danh sách nhiệm vụ chi tiết.
-   - `docs/logs/`: Lưu trữ nhật ký hoạt động của Agent.
-   - `docs/walkthroughs/`: Lưu trữ hướng dẫn thực hiện.
-   - `docs/producs/`: Lưu trữ đặc tả sản phẩm (specs, PRD).
-
-2. **Khởi tạo File mẫu (Tùy chọn)**:
-   Trong mỗi thư mục, tạo một file `README.md` ngắn gọn mô tả mục đích của thư mục đó.
-
-## Lệnh thực thi (Dành cho Agent):
-
-// turbo
-```pwsh
-$docsDir = "docs"
-if (-not (Test-Path $docsDir)) {
-    New-Item -ItemType Directory -Path $docsDir -Force
-    Write-Host "Created base directory: $docsDir"
-}
-
-$dirs = @("lessons", "reports", "plans", "status", "tasks", "logs", "walkthroughs", "producs")
-foreach ($dir in $dirs) {
-    $targetPath = Join-Path $docsDir $dir
-    if (-not (Test-Path $targetPath)) {
-        New-Item -ItemType Directory -Path $targetPath -Force
-        Write-Host "Created directory: $targetPath"
-    }
-}
-```
-
-## Báo cáo kết quả:
-Sau khi hoàn thành, báo cáo danh sách các thư mục đã được khởi tạo thành công.
+---
+description: Tự động khởi tạo cấu trúc thư mục tài liệu cho dự án Pilo Masterkit.
+---
+
+# Workflow: Khởi tạo Thư mục Tài liệu (Documentation Init)
+
+Quy trình này tự động tạo các thư mục cần thiết để quản lý tài liệu, báo cáo và nhiệm vụ theo chuẩn Pilo Masterkit.
+
+## Các bước thực hiện:
+
+1. **Kiểm tra và Tạo Thư mục**:
+   Tạo thư mục `docs/` ở thư mục gốc của dự án (nếu chưa có), sau đó tạo 8 thư mục con bên trong `docs/`:
+   - `docs/lessons/`: Lưu trữ bài học kinh nghiệm.
+   - `docs/reports/`: Lưu trữ báo cáo tiến độ và audit.
+   - `docs/plans/`: Lưu trữ kế hoạch triển khai.
+   - `docs/status/`: Lưu trữ trạng thái dự án.
+   - `docs/tasks/`: Lưu trữ danh sách nhiệm vụ chi tiết.
+   - `docs/logs/`: Lưu trữ nhật ký hoạt động của Agent.
+   - `docs/walkthroughs/`: Lưu trữ hướng dẫn thực hiện.
+   - `docs/producs/`: Lưu trữ đặc tả sản phẩm (specs, PRD).
+
+2. **Khởi tạo File mẫu (Tùy chọn)**:
+   Trong mỗi thư mục, tạo một file `README.md` ngắn gọn mô tả mục đích của thư mục đó.
+
+## Lệnh thực thi (Dành cho Agent):
+
+// turbo
+```pwsh
+$docsDir = "docs"
+if (-not (Test-Path $docsDir)) {
+    New-Item -ItemType Directory -Path $docsDir -Force
+    Write-Host "Created base directory: $docsDir"
+}
+
+$dirs = @("lessons", "reports", "plans", "status", "tasks", "logs", "walkthroughs", "producs")
+foreach ($dir in $dirs) {
+    $targetPath = Join-Path $docsDir $dir
+    if (-not (Test-Path $targetPath)) {
+        New-Item -ItemType Directory -Path $targetPath -Force
+        Write-Host "Created directory: $targetPath"
+    }
+}
+```
+
+## Báo cáo kết quả:
+Sau khi hoàn thành, báo cáo danh sách các thư mục đã được khởi tạo thành công.

package/.agent/workflows/instinct-import.md

@@ -44,7 +44,7 @@ Import instincts from local file paths or HTTP(S) URLs.
 ## Import Process
 
 ```
-📥 Importing instincts from: team-instincts.yaml
+ Importing instincts from: team-instincts.yaml
 ================================================
 
 Found 12 instincts to import.
@@ -60,12 +60,12 @@ These will be added:
 
 ## Duplicate Instincts (3)
 Already have similar instincts:
-  ⚠️ prefer-functional-style
+  WARNING: prefer-functional-style
      Local: 0.8 confidence, 12 observations
      Import: 0.7 confidence
      → Keep local (higher confidence)
 
-  ⚠️ test-first-workflow
+  WARNING: test-first-workflow
      Local: 0.75 confidence
      Import: 0.9 confidence
      → Update to import (higher confidence)
@@ -102,7 +102,7 @@ project_name: "my-project"
 
 After import:
 ```
-✅ Import complete!
+PASS: Import complete!
 
 Added: 8 instincts
 Updated: 1 instinct

package/.agent/workflows/jira.md

@@ -0,0 +1,106 @@
+---
+description: Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
+---
+
+# Jira Command
+
+Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status.
+
+## Usage
+
+```
+/jira get <TICKET-KEY>          # Fetch and analyze a ticket
+/jira comment <TICKET-KEY>      # Add a progress comment
+/jira transition <TICKET-KEY>   # Change ticket status
+/jira search <JQL>              # Search issues with JQL
+```
+
+## What This Command Does
+
+1. **Get & Analyze** — Fetch a Jira ticket and extract requirements, acceptance criteria, test scenarios, and dependencies
+2. **Comment** — Add structured progress updates to a ticket
+3. **Transition** — Move a ticket through workflow states (To Do → In Progress → Done)
+4. **Search** — Find issues using JQL queries
+
+## How It Works
+
+### `/jira get <TICKET-KEY>`
+
+1. Fetch the ticket from Jira (via MCP `jira_get_issue` or REST API)
+2. Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues
+3. Optionally fetch comments for additional context
+4. Produce a structured analysis:
+
+```
+Ticket: PROJ-1234
+Summary: [title]
+Status: [status]
+Priority: [priority]
+Type: [Story/Bug/Task]
+
+Requirements:
+1. [extracted requirement]
+2. [extracted requirement]
+
+Acceptance Criteria:
+- [ ] [criterion from ticket]
+
+Test Scenarios:
+- Happy Path: [description]
+- Error Case: [description]
+- Edge Case: [description]
+
+Dependencies:
+- [linked issues, APIs, services]
+
+Recommended Next Steps:
+- /plan to create implementation plan
+- /tdd to implement with tests first
+```
+
+### `/jira comment <TICKET-KEY>`
+
+1. Summarize current session progress (what was built, tested, committed)
+2. Format as a structured comment
+3. Post to the Jira ticket
+
+### `/jira transition <TICKET-KEY>`
+
+1. Fetch available transitions for the ticket
+2. Show options to user
+3. Execute the selected transition
+
+### `/jira search <JQL>`
+
+1. Execute the JQL query against Jira
+2. Return a summary table of matching issues
+
+## Prerequisites
+
+This command requires Jira credentials. Choose one:
+
+**Option A — MCP Server (recommended):**
+Add `jira` to your `mcpServers` config (see `mcp-configs/mcp-servers.json` for the template).
+
+**Option B — Environment variables:**
+```bash
+export JIRA_URL="https://yourorg.atlassian.net"
+export JIRA_EMAIL="your.email@example.com"
+export JIRA_API_TOKEN="your-api-token"
+```
+
+If credentials are missing, stop and direct the user to set them up.
+
+## Integration with Other Commands
+
+After analyzing a ticket:
+- Use `/plan` to create an implementation plan from the requirements
+- Use `/tdd` to implement with test-driven development
+- Use `/code-review` after implementation
+- Use `/jira comment` to post progress back to the ticket
+- Use `/jira transition` to move the ticket when work is complete
+
+## Related
+
+- **Skill:** `skills/jira-integration/`
+- **MCP config:** `mcp-configs/mcp-servers.json` → `jira`

package/.agent/workflows/kotlin-build.md

@@ -131,7 +131,7 @@ $ ./gradlew test
 | Files modified | 2 |
 | Remaining issues | 0 |
 
-Build Status: ✅ SUCCESS
+Build Status: PASS: SUCCESS
 ````
 
 ## Common Errors Fixed

package/.agent/workflows/kotlin-review.md

@@ -80,7 +80,7 @@ Agent:
 ## Static Analysis Results
 ✓ Build: Successful
 ✓ detekt: No issues
-⚠ ktlint: 2 formatting warnings
+WARNING: ktlint: 2 formatting warnings
 
 ## Issues Found
 
@@ -116,16 +116,16 @@ launch {
 - HIGH: 1
 - MEDIUM: 0
 
-Recommendation: ❌ Block merge until CRITICAL issue is fixed
+Recommendation: FAIL: Block merge until CRITICAL issue is fixed
 ````
 
 ## Approval Criteria
 
 | Status | Condition |
 |--------|-----------|
-| ✅ Approve | No CRITICAL or HIGH issues |
-| ⚠️ Warning | Only MEDIUM issues (merge with caution) |
-| ❌ Block | CRITICAL or HIGH issues found |
+| PASS: Approve | No CRITICAL or HIGH issues |
+| WARNING: Warning | Only MEDIUM issues (merge with caution) |
+| FAIL: Block | CRITICAL or HIGH issues found |
 
 ## Integration with Other Commands
 

package/.agent/workflows/learn-eval.md

@@ -73,19 +73,19 @@ origin: auto-extracted
    | **Absorb into [X]** | Should be appended to an existing skill | Show target skill and additions → Step 6 |
    | **Drop** | Trivial, redundant, or too abstract | Explain reasoning and stop |
 
-   **Guideline dimensions** (informing the verdict, not scored):
+**Guideline dimensions** (informing the verdict, not scored):
 
-   - **Specificity & Actionability**: Contains code examples or commands that are immediately usable
-   - **Scope Fit**: Name, trigger conditions, and content are aligned and focused on a single pattern
-   - **Uniqueness**: Provides value not covered by existing skills (informed by checklist results)
-   - **Reusability**: Realistic trigger scenarios exist in future sessions
+- **Specificity & Actionability**: Contains code examples or commands that are immediately usable
+- **Scope Fit**: Name, trigger conditions, and content are aligned and focused on a single pattern
+- **Uniqueness**: Provides value not covered by existing skills (informed by checklist results)
+- **Reusability**: Realistic trigger scenarios exist in future sessions
 
 6. **Verdict-specific confirmation flow**
 
-   - **Improve then Save**: Present the required improvements + revised draft + updated checklist/verdict after one re-evaluation; if the revised verdict is **Save**, save after user confirmation, otherwise follow the new verdict
-   - **Save**: Present save path + checklist results + 1-line verdict rationale + full draft → save after user confirmation
-   - **Absorb into [X]**: Present target path + additions (diff format) + checklist results + verdict rationale → append after user confirmation
-   - **Drop**: Show checklist results + reasoning only (no confirmation needed)
+- **Improve then Save**: Present the required improvements + revised draft + updated checklist/verdict after one re-evaluation; if the revised verdict is **Save**, save after user confirmation, otherwise follow the new verdict
+- **Save**: Present save path + checklist results + 1-line verdict rationale + full draft → save after user confirmation
+- **Absorb into [X]**: Present target path + additions (diff format) + checklist results + verdict rationale → append after user confirmation
+- **Drop**: Show checklist results + reasoning only (no confirmation needed)
 
 7. Save / Absorb to the determined location
 

package/.agent/workflows/multi-plan.md

@@ -203,19 +203,19 @@ Synthesize both analyses, generate **Step-by-step Implementation Plan**:
 2. Save plan to `.claude/plan/<feature-name>.md` (extract feature name from requirement, e.g., `user-auth`, `payment-module`)
 3. Output prompt in **bold text** (MUST use actual saved file path):
 
-   ---
-   **Plan generated and saved to `.claude/plan/actual-feature-name.md`**
+---
+**Plan generated and saved to `.claude/plan/actual-feature-name.md`**
 
-   **Please review the plan above. You can:**
-   - **Modify plan**: Tell me what needs adjustment, I'll update the plan
-   - **Execute plan**: Copy the following command to a new session
+**Please review the plan above. You can:**
+- **Modify plan**: Tell me what needs adjustment, I'll update the plan
+- **Execute plan**: Copy the following command to a new session
 
-   ```
-   /ccg:execute .claude/plan/actual-feature-name.md
-   ```
-   ---
+```
+/ccg:execute .claude/plan/actual-feature-name.md
+```
+---
 
-   **NOTE**: The `actual-feature-name.md` above MUST be replaced with the actual saved filename!
+**NOTE**: The `actual-feature-name.md` above MUST be replaced with the actual saved filename!
 
 4. **Immediately terminate current response** (Stop here. No more tool calls.)
 

package/.agent/workflows/orchestrate.md

@@ -1,139 +1,43 @@
 ---
-description: Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
+description: Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly.
 ---
 
-# Orchestrate Command
+# Orchestrate Command (Legacy Shim)
 
-Sequential agent workflow for complex tasks.
+Use this only if you still invoke `/orchestrate`. The maintained orchestration guidance lives in `skills/dmux-workflows/SKILL.md` and `skills/autonomous-agent-harness/SKILL.md`.
 
-## Usage
+## Canonical Surface
 
-`/orchestrate [workflow-type] [task-description]`
+- Prefer `dmux-workflows` for parallel panes, worktrees, and multi-agent splits.
+- Prefer `autonomous-agent-harness` for longer-running loops, governance, scheduling, and control-plane style execution.
+- Keep this file only as a compatibility entry point.
 
-## Workflow Types
-
-### feature
-Full feature implementation workflow:
-```
-planner -> tdd-guide -> code-reviewer -> security-reviewer
-```
-
-### bugfix
-Bug investigation and fix workflow:
-```
-planner -> tdd-guide -> code-reviewer
-```
-
-### refactor
-Safe refactoring workflow:
-```
-architect -> code-reviewer -> tdd-guide
-```
-
-### security
-Security-focused review:
-```
-security-reviewer -> code-reviewer -> architect
-```
-
-## Execution Pattern
-
-For each agent in the workflow:
-
-1. **Invoke agent** with context from previous agent
-2. **Collect output** as structured handoff document
-3. **Pass to next agent** in chain
-4. **Aggregate results** into final report
-
-## Handoff Document Format
-
-Between agents, create handoff document:
-
-```markdown
-## HANDOFF: [previous-agent] -> [next-agent]
-
-### Context
-[Summary of what was done]
-
-### Findings
-[Key discoveries or decisions]
-
-### Files Modified
-[List of files touched]
-
-### Open Questions
-[Unresolved items for next agent]
-
-### Recommendations
-[Suggested next steps]
-```
-
-## Example: Feature Workflow
-
-```
-/orchestrate feature "Add user authentication"
-```
-
-Executes:
-
-1. **Planner Agent**
-   - Analyzes requirements
-   - Creates implementation plan
-   - Identifies dependencies
-   - Output: `HANDOFF: planner -> tdd-guide`
-
-2. **TDD Guide Agent**
-   - Reads planner handoff
-   - Writes tests first
-   - Implements to pass tests
-   - Output: `HANDOFF: tdd-guide -> code-reviewer`
-
-3. **Code Reviewer Agent**
-   - Reviews implementation
-   - Checks for issues
-   - Suggests improvements
-   - Output: `HANDOFF: code-reviewer -> security-reviewer`
-
-4. **Security Reviewer Agent**
-   - Security audit
-   - Vulnerability check
-   - Final approval
-   - Output: Final Report
-
-## Final Report Format
+## Arguments
 
-```
-ORCHESTRATION REPORT
-====================
-Workflow: feature
-Task: Add user authentication
-Agents: planner -> tdd-guide -> code-reviewer -> security-reviewer
+`$ARGUMENTS`
 
-SUMMARY
--------
-[One paragraph summary]
+## Delegation
 
-AGENT OUTPUTS
--------------
-Planner: [summary]
-TDD Guide: [summary]
-Code Reviewer: [summary]
+Apply the orchestration skills instead of maintaining a second workflow spec here.
+- Start with `dmux-workflows` for split/parallel execution.
+- Pull in `autonomous-agent-harness` when the user is really asking for persistent loops, governance, or operator-layer behavior.
+- Keep handoffs structured, but let the skills define the maintained sequencing rules.
 Security Reviewer: [summary]
 
-FILES CHANGED
--------------
+### FILES CHANGED
+
 [List all files modified]
 
-TEST RESULTS
-------------
+### TEST RESULTS
+
 [Test pass/fail summary]
 
-SECURITY STATUS
----------------
+### SECURITY STATUS
+
 [Security findings]
 
-RECOMMENDATION
---------------
+### RECOMMENDATION
+
 [SHIP / NEEDS WORK / BLOCKED]
 ```
 
@@ -207,7 +111,7 @@ Telemetry:
 
 This keeps planner, implementer, reviewer, and loop workers legible from the operator surface.
 
-## Arguments
+## Workflow Arguments
 
 $ARGUMENTS:
 - `feature <description>` - Full feature workflow

package/.agent/workflows/plan.md

@@ -107,6 +107,8 @@ After planning:
 - Use `/build-fix` if build errors occur
 - Use `/code-review` to review completed implementation
 
+> **Need deeper planning?** Use `/prp-plan` for artifact-producing planning with PRD integration, codebase analysis, and pattern extraction. Use `/prp-implement` to execute those plans with rigorous validation loops.
+
 ## Related Agents
 
 This command invokes the `planner` agent provided by ECC.

package/.agent/workflows/preview.md

@@ -1,81 +1,81 @@
----
-description: Preview server start, stop, and status check. Local development server management.
----
-
-# /preview - Preview Management
-
-$ARGUMENTS
-
----
-
-## Task
-
-Manage preview server: start, stop, status check.
-
-### Commands
-
-```
-/preview           - Show current status
-/preview start     - Start server
-/preview stop      - Stop server
-/preview restart   - Restart
-/preview check     - Health check
-```
-
----
-
-## Usage Examples
-
-### Start Server
-```
-/preview start
-
-Response:
-🚀 Starting preview...
-   Port: 3000
-   Type: Next.js
-
-✅ Preview ready!
-   URL: http://localhost:3000
-```
-
-### Status Check
-```
-/preview
-
-Response:
-=== Preview Status ===
-
-🌐 URL: http://localhost:3000
-📁 Project: C:/projects/my-app
-🏷️ Type: nextjs
-💚 Health: OK
-```
-
-### Port Conflict
-```
-/preview start
-
-Response:
-⚠️ Port 3000 is in use.
-
-Options:
-1. Start on port 3001
-2. Close app on 3000
-3. Specify different port
-
-Which one? (default: 1)
-```
-
----
-
-## Technical
-
-Auto preview uses `auto_preview.py` script:
-
-```bash
-python .agent/scripts/auto_preview.py start [port]
-python .agent/scripts/auto_preview.py stop
-python .agent/scripts/auto_preview.py status
-```
-
+---
+description: Preview server start, stop, and status check. Local development server management.
+---
+
+# /preview - Preview Management
+
+$ARGUMENTS
+
+---
+
+## Task
+
+Manage preview server: start, stop, status check.
+
+### Commands
+
+```
+/preview           - Show current status
+/preview start     - Start server
+/preview stop      - Stop server
+/preview restart   - Restart
+/preview check     - Health check
+```
+
+---
+
+## Usage Examples
+
+### Start Server
+```
+/preview start
+
+Response:
+🚀 Starting preview...
+   Port: 3000
+   Type: Next.js
+
+✅ Preview ready!
+   URL: http://localhost:3000
+```
+
+### Status Check
+```
+/preview
+
+Response:
+=== Preview Status ===
+
+🌐 URL: http://localhost:3000
+📁 Project: C:/projects/my-app
+🏷️ Type: nextjs
+💚 Health: OK
+```
+
+### Port Conflict
+```
+/preview start
+
+Response:
+⚠️ Port 3000 is in use.
+
+Options:
+1. Start on port 3001
+2. Close app on 3000
+3. Specify different port
+
+Which one? (default: 1)
+```
+
+---
+
+## Technical
+
+Auto preview uses `auto_preview.py` script:
+
+```bash
+python .agent/scripts/auto_preview.py start [port]
+python .agent/scripts/auto_preview.py stop
+python .agent/scripts/auto_preview.py status
+```
+