@tiqora/tiqora 0.0.2-dev

package/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "@tiqora/tiqora",
+  "version": "0.0.2-dev",
+  "description": "Agentic delivery CLI for solo devs: challenge tickets, orchestrate PM/SM/Dev flows, and keep execution synced.",
+  "type": "module",
+  "main": "dist/index.cjs",
+  "module": "dist/index.mjs",
+  "files": [
+    "dist",
+    "templates",
+    "_tiqora",
+    "README.md"
+  ],
+  "bin": {
+    "tiqora": "./dist/index.cjs"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "scripts": {
+    "build": "tsup",
+    "prepack": "npm run build",
+    "test": "npm run build && vitest run"
+  },
+  "dependencies": {
+    "@clack/prompts": "^1.0.0",
+    "commander": "^14.0.0"
+  },
+  "devDependencies": {
+    "@types/node": "^24.0.0",
+    "tsup": "^8.5.0",
+    "typescript": "^5.9.0",
+    "vitest": "^4.0.0"
+  }
+}

package/templates/commands/tiq-agent-dev.md

@@ -0,0 +1,17 @@
+---
+description: 'Launch the tiqora Developer agent for implementation guidance and execution support'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:agent:dev`
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the Developer agent:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_tiqora/agents/dev.md
+2. READ its entire contents and apply activation, persona, menu, and rules exactly
+3. Resolve config using project `.tiqora.yaml` (required) + `~/.tiqora/config.yaml` (optional base)
+4. YOU MUST ALWAYS SPEAK OUTPUT in the effective `communication_language`
+5. Generate artifacts in `document_language` unless user explicitly requests otherwise
+6. When a workflow menu item is selected, execute via @_tiqora/core/tasks/workflow.xml with the workflow yaml path defined by the agent menu
+</steps>

package/templates/commands/tiq-agent-pm.md

@@ -0,0 +1,18 @@
+---
+description: 'Launch the tiqora Product Manager agent for requirement clarity and prioritization'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:agent:pm`
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the Product Manager agent:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_tiqora/agents/pm.md
+2. READ its entire contents and apply activation, persona, menu, and rules exactly
+3. Resolve config using project `.tiqora.yaml` (required) + `~/.tiqora/config.yaml` (optional base)
+4. YOU MUST ALWAYS SPEAK OUTPUT in the effective `communication_language`
+5. Generate artifacts in `document_language` unless user explicitly requests otherwise
+6. Keep decisions anchored on user value, measurable outcomes, and explicit scope boundaries
+7. When a workflow menu item is selected, execute via @_tiqora/core/tasks/workflow.xml with the workflow yaml path defined by the agent menu
+</steps>

package/templates/commands/tiq-agent-sm.md

@@ -0,0 +1,18 @@
+---
+description: 'Launch the tiqora Scrum Master agent for planning, sequencing, and sprint flow'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:agent:sm`
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the Scrum Master agent:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_tiqora/agents/sm.md
+2. READ its entire contents and apply activation, persona, menu, and rules exactly
+3. Resolve config using project `.tiqora.yaml` (required) + `~/.tiqora/config.yaml` (optional base)
+4. YOU MUST ALWAYS SPEAK OUTPUT in the effective `communication_language`
+5. Generate artifacts in `document_language` unless user explicitly requests otherwise
+6. Do not execute coding tasks directly; route implementation to `/tiq:workflow:dev-story`
+7. When a workflow menu item is selected, execute via @_tiqora/core/tasks/workflow.xml with the workflow yaml path defined by the agent menu
+</steps>

package/templates/commands/tiq-workflow-create-story.md

@@ -0,0 +1,21 @@
+---
+description: 'Run the tiqora create-story workflow to produce implementation-ready story specs'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:workflow:create-story`
+
+## Workflow Intent
+
+Generate a structured story with clear acceptance criteria and implementation scope.
+
+## Required Inputs
+
+- Project context from `.tiqora.yaml`
+- Ticket intent or problem statement
+- Delivery constraints
+
+## Output
+
+- Story artifact in `.tiqora/workflows/steps/`
+- Updated sprint tracking status

package/templates/commands/tiq-workflow-create-ticket.md

@@ -0,0 +1,21 @@
+---
+description: 'Run the tiqora create-ticket workflow to draft and create a ticket in the configured PM tool'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:workflow:create-ticket`
+
+## Workflow Intent
+
+Create a structured ticket with clear acceptance criteria and PM-aligned metadata.
+
+## Required Inputs
+
+- `.tiqora.yaml`
+- Problem statement and expected outcome
+- Priority and constraints
+
+## Output
+
+- Created ticket in configured PM tool (or queued sync if unavailable)
+- Local ticket artifact for traceability in `.tiqora/workflows/steps/`

package/templates/commands/tiq-workflow-dev-story.md

@@ -0,0 +1,16 @@
+---
+description: 'Execute tiqora dev-story workflow (config merge, ticket context, challenge gate, branch/run-state, implementation flow)'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:workflow:dev-story`
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded, except when workflow instructions explicitly require loading PM persona for challenge and Developer persona for implementation:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_tiqora/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_tiqora/workflows/4-implementation/dev-story/workflow.yaml
+3. Pass the yaml path _tiqora/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/templates/commands/tiq-workflow-fetch-project-context.md

@@ -0,0 +1,21 @@
+---
+description: 'Run the tiqora fetch-project-context workflow to gather scoped project/tool context'
+disable-model-invocation: true
+---
+
+Command Trigger: `/tiq:workflow:fetch-project-context`
+
+## Workflow Intent
+
+Collect project metadata, tool configuration, active branch details, and relevant prior decisions.
+
+## Required Inputs
+
+- `.tiqora.yaml`
+- Current repository state
+- Optional PM ticket id
+
+## Output
+
+- Context artifact in `.tiqora/workflows/steps/`
+- Reusable context pointer for subsequent workflow steps

package/templates/config/tiqora.yaml.tpl

@@ -0,0 +1,3 @@
+pm_tool: {{pm_tool}}
+git_host: {{git_host}}
+branch_pattern: '{{branch_pattern}}'