Natural language wrapper for ContextKit planning commands - automatically triggers /ctxk:plan commands when users request planning assistance
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: contextkit-planning-trigger
description: Natural language wrapper for ContextKit planning commands - automatically triggers /ctxk:plan commands when users request planning assistance
schema_version: 1.0
---
# contextkit-planning-trigger
**Type:** ANALYSIS-ONLY
**DAIC Modes:** DISCUSS, ALIGN, IMPLEMENT, CHECK (all modes)
**Priority:** Medium
## Trigger Reference
This skill activates on:
- **Keywords:** "plan this", "how should I approach", "create plan", "quick plan", "break down into steps", "research tech", "planning", "approach", "strategy", "implementation plan"
- **Intent Patterns:** `(plan|approach|strategy).*(this|feature|task)`, `how.*?(approach|implement|structure)`, `break.*?down.*?steps`, `research.*(tech|technology|options)`, `create.*(plan|strategy)`
From: `skill-rules.json` - contextkit-planning-trigger configuration
## Purpose
Automatically trigger ContextKit planning commands (`/ctxk:plan:quick`, `/ctxk:plan:1-spec`, `/ctxk:plan:2-research-tech`, `/ctxk:plan:3-steps`) when users request planning assistance using natural language.
## Core Behavior
In any DAIC mode:
1. **Planning Intent Detection**
- Detect planning requests from natural language
- Route to appropriate ContextKit planning command
2. **Command Routing**
- **Quick planning:** "plan this feature" → `/ctxk:plan:quick`
- **Detailed spec:** "create detailed spec" → `/ctxk:plan:1-spec`
- **Tech research:** "research technology options" → `/ctxk:plan:2-research-tech`
- **Implementation steps:** "break down into steps" → `/ctxk:plan:3-steps`
## Natural Language Examples
**Triggers this skill:**
- ✓ "Plan this feature"
- ✓ "How should I approach this?"
- ✓ "Break down into steps"
- ✓ "Research tech options"
- ✓ "Create implementation plan"
## Safety Guardrails
**ANALYSIS-ONLY RULES:**
- ✓ NEVER call write tools
- ✓ Only invokes ContextKit planning commands (read-only)
- ✓ Safe to run in any DAIC mode
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...