一键导入
liaison-workflows
Task management and workflow patterns using liaison. Use when managing tasks, creating workflows, or working with task-driven automation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Task management and workflow patterns using liaison. Use when managing tasks, creating workflows, or working with task-driven automation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | liaison-workflows |
| description | Task management and workflow patterns using liaison. Use when managing tasks, creating workflows, or working with task-driven automation. |
| license | MIT |
| metadata | {"author":"liaison-toolkit","version":"2.0"} |
Complete guide to task management and workflow automation using the Liaison CLI.
Use this skill when:
liaison task createUse liaison task create to create new tasks:
# Basic task
liaison task create "Fix security vulnerability"
# With description
liaison task create "Fix security vulnerability" --description "Patch XSS in login form"
# With priority
liaison task create "Fix security vulnerability" --priority critical
# With auto-trigger
liaison task create "Security audit required" --auto-trigger "security-response"
# With assignment
liaison task create "Review pull request" --assigned-to @username
Check task status with liaison task list:
# List all tasks
liaison task list
# Filter by status
liaison task list --status closed
# Filter by priority
liaison task list --priority critical
# Output as JSON
liaison task list --format json
Update task status with liaison task update:
# Mark as in-progress
liaison task update TASK-ID --status in-progress
# Mark as completed
liaison task update TASK-ID --status closed
# Add assignee
liaison task update TASK-ID --assigned-to @username
Tasks automatically trigger workflows based on priority:
| Priority | Auto-Triggered Workflow |
|---|---|
| critical | security-response |
| high | high-priority-response |
| medium | standard-workflow |
| low | backlog-workflow |
Example:
liaison task create "Critical security issue" --priority critical
# Automatically triggers security-response workflow
Tasks can specify which workflow to trigger:
liaison task create "Update documentation" --auto-trigger "documentation-update"
Available keywords:
security → security-response workflowbug → bug-fix workflowproduction → deployment workflowdocumentation → documentation-update workflowtesting → qa-testing workflowForce a specific workflow regardless of task content:
liaison task create "Custom task" --auto-trigger "custom-workflow"
Liaison implements complete task-driven workflow automation:
The system creates a virtuous cycle where work generates more work:
User Task → Workflow → Subtasks → More Tasks → More Workflows → ...
This enables:
Liaison supports multiple workflow types:
Triggered by critical priority tasks handling security issues.
Auto-Created Subtasks:
Triggered by tasks containing "bug" or production keywords.
Auto-Created Subtasks:
Triggered by documentation tasks.
Process:
Triggered by high priority tasks.
Process:
Triggered by medium priority tasks.
Process:
Triggered by QA workflows.
Process:
Workflows are defined in configuration files. Create custom workflows:
# List available workflows
liaison workflow list
# Create new workflow
liaison workflow create "code-review" --trigger "task-created:tag=pull-request"
Track workflow execution:
# Workflow status
liaison workflow status
# Execution history
liaison workflow history --limit 10
Use Descriptive Titles
✅ Good: "Security: Fix XSS in login form"
❌ Bad: "Fix security thing"
Set Appropriate Priority
--priority critical # Security, production outages
--priority high # Production bugs, performance issues
--priority medium # Feature requests, improvements
--priority low # Documentation, minor fixes
Include Auto-Triggers Wisely
# Good - Use specific workflows
liaison task create "Add authentication" --auto-trigger "security-response"
# Avoid - Don't over-trigger on everything
# liaison task create "Update docs" --no-auto-trigger
Write Clear Descriptions
# Good
"Implement OAuth2 authentication using JWT tokens"
# Bad
"Auth stuff"
Define Clear Triggers
Keep Workflows Focused
Monitor Workflow Performance
liaison workflow metrics
liaison workflow history
`
Tasks automatically check for duplicates before creation:
# Default behavior (checks for 80% similarity)
liaison task create "New feature"
# Bypass check (only use for intentional duplicates)
liaison task create "Known duplicate" --force-create
# Disable check entirely (batch operations)
liaison task create --no-check-duplicates task1 task2 task3
User: "Found security issue"
Process:
1. liaison task create "Investigate XSS vulnerability" --priority critical
2. Automatically triggers: security-response workflow
3. Workflow creates: investigation, patch, verification tasks
4. Complete verification → patch deployed
User: "Add user authentication"
Process:
1. liaison task create "Design auth system" --priority medium
2. liaison task create "Implement JWT tokens" --auto-trigger "development-workflow"
3. liaison task create "Write auth tests" --auto-trigger "qa-testing"
4. liaison task create "Deploy to staging" --auto-trigger "deployment-workflow"
5. Development workflow manages all subtasks automatically
User: "Update API docs"
Process:
1. liaison task create "Review current docs" --priority low
2. Development workflow triggers automatically
3. Documentation workflow processes all changes
4. Generate changelog and create PR
This skill works alongside other skills:
Combining skills for complex automation:
User: "Add new user onboarding feature"
Automation:
1. [Liaison Workflows] Creates tasks for design, implementation, testing
2. [Git Automation] Creates feature branch with proper naming
3. [Library Research] Researches existing auth libraries
4. [QA Testing] Validates all changes
5. [Deployment Workflow] Deploys to staging
6. Automatic triggers coordinate all workflows
liaison, task, workflow, automation, task-driven, triggers, auto-trigger, subtasks, security, bug-fix, deployment, testing, qa, priorities, closed-loop
CLI development patterns with Commander.js, argument parsing, and user experience best practices. Use when creating commands, handling options, formatting output, or building CLI tools.
Release workflow with changesets, version bumping, changelog generation, and npm publishing. Use when preparing releases, managing versions, or publishing to npm.
Security scanning with dependency audits, secret detection, static analysis, and vulnerability management. Use when checking for vulnerabilities, scanning dependencies, or enforcing security gates.
Multi-agent coordination patterns for delegating work between specialized agents, managing agent roles, and orchestrating workflows across multiple AI agents.
Testing patterns with Bun test runner, coverage thresholds, mocking, and CI/CD integration. Use when writing tests, organizing test files, or setting up quality gates.
Bun build system, development workflow, and TypeScript patterns. Use when working with Bun projects, setting up development environment, or managing dependencies with Bun package manager.