clikit-plugin 0.3.10 → 0.3.12

package/command/import-plan.md

@@ -1,175 +0,0 @@
----
-description: Import tasks from Jira, Notion, Linear, or raw markdown/JSON and convert them into tracked Beads issues with a ready-to-execute plan.
-agent: plan
----
-
-You are the **Plan Agent**. Execute the `/import-plan` command.
-
-## Your Task
-
-Import planning data from external tools (Jira, Notion, Linear, etc.) and convert to internal format.
-
-## Process
-
-### 1. Gather Source Data
-
-Ask user for:
-- Source type (Jira, Notion, Linear, Markdown, JSON)
-- Data to import (URL, file path, or pasted content)
-
-### 2. Parse External Format
-
-**Jira:**
-```
-- Epic → Bead
-- Story/Task → Task (T-XXX)
-- Subtask → Acceptance Criteria
-- Priority → P0/P1/P2 mapping
-- Story Points → Effort (S/M/L/XL)
-```
-
-**Notion:**
-```
-- Page → Bead or Spec
-- Database items → Tasks
-- Properties → Task fields
-```
-
-**Linear:**
-```
-- Project → Bead
-- Issue → Task
-- Labels → Tags
-- Priority → P0/P1/P2 mapping
-```
-
-**Markdown/JSON:**
-```
-- Parse structure
-- Map to Task Schema
-```
-
-### 3. Normalize to Internal Format
-
-Convert each item to Task Schema (`.opencode/schemas.md` §1):
-
-```yaml
-task_id: "T-001"
-title: "[Imported title]"
-type: task | bug | feature | chore
-status: not_started
-assignee: build | fe | be | mobile | devops
-priority: P0 | P1 | P2
-effort: S | M | L | XL
-dependencies: []
-description: "[Imported description]"
-input: []
-output: []
-boundaries: []
-acceptance_criteria: []
-```
-
-### 4. Validate Against Spec
-
-- Check if `spec.md` exists
-- If yes: validate imported tasks align with spec
-- If no: suggest creating spec first or generate from import
-
-### 5. Identify Gaps
-
-| Gap Type | Action |
-|----------|--------|
-| Missing acceptance criteria | Flag for user input |
-| Missing dependencies | Ask user to define |
-| Unclear scope | Mark as "Needs Clarification" |
-| Missing effort estimates | Suggest based on description |
-
-### 6. Generate plan.md
-
-Create plan at `.opencode/memory/plans/YYYY-MM-DD-<feature>.md` using template `@.opencode/memory/_templates/plan.md`
-
-### 7. Create Beads
-
-For each task:
-```
-mcp__beads_village__add(
-  title: "[Task title]",
-  desc: "[Description]",
-  typ: "[type]",
-  pri: [0-4],
-  deps: ["task:T-XXX"]
-)
-```
-
-## Output Format
-
-```markdown
-## Import Summary
-
-### Source
-- **Type:** [Jira/Notion/Linear/etc.]
-- **Items Found:** [count]
-
-### Imported Tasks
-
-| ID | Title | Type | Effort | Priority | Status |
-|----|-------|------|--------|----------|--------|
-| T-001 | [Title] | feature | M | P1 | Imported ✅ |
-| T-002 | [Title] | task | S | P2 | Needs AC ⚠️ |
-
-### Gaps Identified
-
-- [ ] T-002: Missing acceptance criteria
-- [ ] T-003: Dependencies unclear
-
-### Artifacts Created
-
-- Plan: `.opencode/memory/plans/YYYY-MM-DD-feature.md`
-- Beads: [count] tasks added to beads village
-
-### Next Steps
-
-1. Review and fill gaps
-2. Get user approval on plan
-3. `/start` to begin execution
-```
-
-## Field Mapping Reference
-
-### Priority Mapping
-
-| External | Internal |
-|----------|----------|
-| Highest, Critical, P0 | P0 |
-| High, P1 | P1 |
-| Medium, Normal, P2 | P2 |
-| Low, P3, P4 | P2 |
-
-### Effort Mapping
-
-| External | Internal |
-|----------|----------|
-| 1-2 points, XS | S |
-| 3-5 points, S, M | M |
-| 8-13 points, L | L |
-| 21+ points, XL | XL |
-
-### Type Mapping
-
-| External | Internal |
-|----------|----------|
-| Story, Feature, Enhancement | feature |
-| Bug, Defect | bug |
-| Task, Subtask | task |
-| Chore, Maintenance, Tech Debt | chore |
-
-## Rules
-
-- ✅ ALWAYS validate against Task Schema
-- ✅ ALWAYS preserve original IDs as reference
-- ✅ ALWAYS flag gaps rather than guess
-- ✅ ALWAYS get user approval before proceeding
-- ❌ NEVER auto-fill critical fields (AC, dependencies)
-- ❌ NEVER import without creating beads
-
-Now, what would you like to import? Please provide the source type and data.

package/command/issue.md

@@ -1,109 +0,0 @@
----
-description: Instantly capture any task, bug, or idea as a tracked Beads issue with priority and tags — no full spec needed.
-agent: build
----
-
-You are creating a **quick issue** in beads village.
-
-## Your Task
-
-Rapidly create an issue/task without full spec process.
-
-## Usage
-
-```
-/issue [title]
-```
-
-Or just `/issue` and I'll ask for details.
-
-## Process
-
-### 1. Gather Minimal Info
-
-- **Title:** What needs to be done? (required)
-- **Type:** task | bug | feature | chore (default: task)
-- **Priority:** P0=critical, P1=high, P2=normal (default: P2)
-- **Description:** Brief context (optional)
-- **Tags:** fe, be, mobile, devops, qa (optional)
-
-### 2. Create in Beads
-
-```
-mcp__beads_village__add(
-  title: "[title]",
-  typ: "[type]",
-  pri: [priority],
-  desc: "[description]",
-  tags: ["tag1", "tag2"]
-)
-```
-
-### 3. Confirm Creation
-
-## Quick Templates
-
-### Bug Report
-```
-/issue Bug: [what's broken]
-```
-→ Creates with `typ: "bug"`, `pri: 1`
-
-### Feature Request
-```
-/issue Feature: [what to add]
-```
-→ Creates with `typ: "feature"`, `pri: 2`
-
-### Quick Task
-```
-/issue [action verb] [thing]
-```
-→ Creates with `typ: "task"`, `pri: 2`
-
-### Chore
-```
-/issue Chore: [maintenance task]
-```
-→ Creates with `typ: "chore"`, `pri: 2`
-
-## Examples
-
-| Input | Result |
-|-------|--------|
-| `/issue Fix login button not working` | Bug, P1 |
-| `/issue Add dark mode support` | Feature, P2 |
-| `/issue Update dependencies` | Chore, P2 |
-| `/issue Refactor auth module` | Task, P2 |
-
-## Output Format
-
-```markdown
-## ✅ Issue Created
-
-**ID:** [bead-id]
-**Title:** [title]
-**Type:** [type]
-**Priority:** P0 | P1 | P2
-**Tags:** [tags]
-
-### Next Steps
-- Start with `/start` (after `/create` generates a plan)
-- View all with `/status`
-```
-
-## Advanced Options
-
-For complex issues, use full form:
-```
-/issue
-Title: [required]
-Type: bug | task | feature | chore
-Priority: P0 | P1 | P2
-Description: [context]
-Tags: fe, be, mobile, devops, qa
-Parent: [parent-id for subtasks]
-Deps: [blocking-issue-ids]
-```
-
-What issue do you want to create?

package/dist/hooks/tilth-first-guard.d.ts

@@ -1,18 +0,0 @@
-/**
- * Tilth-First Guard Hook
- *
- * Hard-enforces explicit tilth CLI usage for the Explore agent before it can
- * fall back to read/grep/glob.
- */
-export interface TilthFirstGuardState {
-    sawTilthAttempt: boolean;
-}
-export declare function isExploreAgent(agent: unknown): boolean;
-export declare function isFallbackNavigationTool(toolName: unknown): boolean;
-export declare function isExplicitTilthCommand(command: unknown): boolean;
-export declare function markTilthAttempt(state?: TilthFirstGuardState): TilthFirstGuardState;
-export declare function shouldBlockTilthFallback(agent: unknown, toolName: unknown, state?: TilthFirstGuardState): boolean;
-export declare function formatTilthFirstGuardWarning(toolName: string): string;
-export declare function formatTilthFirstGuardReason(toolName: string): string;
-export declare function formatTilthFirstGuardPass(command: string): string;
-//# sourceMappingURL=tilth-first-guard.d.ts.map

package/dist/hooks/tilth-first-guard.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"tilth-first-guard.d.ts","sourceRoot":"","sources":["../../src/hooks/tilth-first-guard.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAMH,MAAM,WAAW,oBAAoB;IACnC,eAAe,EAAE,OAAO,CAAC;CAC1B;AAMD,wBAAgB,cAAc,CAAC,KAAK,EAAE,OAAO,GAAG,OAAO,CAEtD;AAED,wBAAgB,wBAAwB,CAAC,QAAQ,EAAE,OAAO,GAAG,OAAO,CAEnE;AAED,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAEhE;AAED,wBAAgB,gBAAgB,CAAC,KAAK,CAAC,EAAE,oBAAoB,GAAG,oBAAoB,CAKnF;AAED,wBAAgB,wBAAwB,CACtC,KAAK,EAAE,OAAO,EACd,QAAQ,EAAE,OAAO,EACjB,KAAK,CAAC,EAAE,oBAAoB,GAC3B,OAAO,CAUT;AAED,wBAAgB,4BAA4B,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAErE;AAED,wBAAgB,2BAA2B,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAEpE;AAED,wBAAgB,yBAAyB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CAEjE"}

package/memory/_digest.md

@@ -1,6 +0,0 @@
-# Memory Digest
-
-> Auto-generated on 2026-04-03. Read-only reference for agents.
-> Source: `.opencode/memory/memory.db`
-
-*No observations found in memory database.*

package/memory/_templates/spec.md

@@ -1,128 +0,0 @@
-# Spec Template
-
-Use this template when creating specifications.
-
-**Output path:** `.opencode/memory/specs/YYYY-MM-DD-<descriptor>.md`
-
----
-
-```markdown
-# Specification: [Title]
-
-**Date:** YYYY-MM-DD
-**Author:** [Name]
-**Status:** Draft | Confirmed
-**bead_id:** [ID]
-
----
-
-## Problem & Context
-
-### Problem Statement
-[Why is this needed?]
-
-### Background
-[Context and history]
-
-### Who is Affected
-[Stakeholders and users impacted]
-
----
-
-## Outcomes
-
-### Success Criteria
-1. [Measurable outcome 1]
-2. [Measurable outcome 2]
-
-### Key Results
-| Outcome | Metric | Target |
-|---------|--------|--------|
-| [Outcome] | [How to measure] | [Target value] |
-
----
-
-## Scope
-
-### In Scope
-- [Feature/capability 1]
-- [Feature/capability 2]
-
-### Out of Scope
-- [Excluded item 1]
-- [Excluded item 2]
-
-### Boundaries
-[Clear boundaries of what this spec covers]
-
----
-
-## Users
-
-### Primary Users
-| User Type | Description | Needs |
-|-----------|-------------|-------|
-| [Type] | [Who they are] | [What they need] |
-
-### Secondary Users
-| User Type | Description | Needs |
-|-----------|-------------|-------|
-
----
-
-## Constraints
-
-### Technical Constraints
-- [Constraint 1]
-
-### Business Constraints
-- [Timeline, budget, etc.]
-
-### Dependencies
-| Dependency | Type | Status |
-|------------|------|--------|
-| [Dependency] | Blocking/Soft | Ready/Pending |
-
----
-
-## Acceptance Criteria
-
-| ID | Criteria | Verification |
-|----|----------|--------------|
-| AC-01 | [Criteria] | [How to verify] |
-| AC-02 | [Criteria] | [How to verify] |
-
-### Execution Notes
-- Preferred workflow mode: `compressed`
-- Expected execution unit: **Task Packet**
-- Beads issue/task is the live execution state
-- Manual-only verification is not allowed unless explicitly marked as follow-up
-
----
-
-## Assumptions
-
-| ID | Assumption | Status | Notes |
-|----|------------|--------|-------|
-| A-01 | [Assumption] | Confirmed/Unconfirmed | [Notes] |
-
----
-
-## Open Questions
-
-- [ ] [Question 1]
-- [ ] [Question 2]
-
-## Planning Handoff Hints
-
-- Likely files in scope: [candidate files/directories]
-- Likely packet boundaries: [how the work should split into 1–3 file packets]
-- Escalate if: [conditions that should trigger re-plan or Oracle]
-
----
-
-## References
-
-- [Link to related docs]
-- [Link to research]
-```