create-groundcrew-ticket
Create Linear tickets that Groundcrew can pick up: assigned to the current Linear user, labeled with agent-*, tied to an implementation repository in the description, optionally linked to parent and blocker tickets, and written to use the core:go implementation workflow.
What this skill does
# Create Groundcrew Ticket Create Linear issues that are ready for Groundcrew dispatch. This skill is agent-agnostic: use the structured Linear capability available in the current agent, following that tool's current schema instead of hard-coding one here. ## Eligibility Contract A Linear issue is Groundcrew-eligible when all of these are true: - It is assigned to the current Linear user. Use the active Linear tool's "current user" value, commonly `me`, when available. - It is in a Todo workflow state. Prefer the Linear state type for Todo when tooling accepts state types. - It has exactly one appropriate `agent-*` label. Use `agent-any` unless the user explicitly asks for a specific model such as `agent-codex` or `agent-claude`. - Its description contains the implementation repository text exactly as Groundcrew can match it, for example `Repository: groundcrew`. - It is a leaf work item. Do not put `agent-*` labels on parent tickets that have children; Groundcrew skips parents with sub-issues. - It is not blocked by non-terminal blockers if the user expects it to start immediately. If blockers are intentional, create `blocked-by` relations and tell the user Groundcrew will wait. Groundcrew resolves the repository by scanning the description for a known repository name. Do not rely on Linear custom fields for repository routing. ## Required Inputs Before creating, know: - `title` - Linear `team` - implementation `repository` - enough task context to write a useful implementation ticket If any required input is missing and cannot be inferred safely, ask a concise question before creating. Repository inference: - If the user names a repository, use that exact value. - Otherwise infer from the current git remote or directory name. - Prefer a value present in `crew.config.ts` `workspace.knownRepositories` when this repo is available. - If multiple known repositories could match the same bare name, ask the user to choose. Optional metadata: - `parent`: parent Linear identifier, for example `ENG-123` - blocked-by relations: tickets this new ticket depends on - blocking relations: tickets this new ticket blocks ## Description Template Use a direct implementation-shaped ticket. Keep the repository line near the top. ```md ## Groundcrew Repository: <repo> Implementation workflow: use the `core:go`/`go` skill when available. If that skill is unavailable, follow this repo's AGENTS.md/CLAUDE.md implementation workflow and run the documented verification. ## Task <what to change> ## Acceptance Criteria - [ ] <observable outcome> ## Notes <links, constraints, parent/blocker context, or "None"> ``` Keep the ticket agent-agnostic. Do not mention Codex-only commands unless the user explicitly requested a Codex-specific ticket. ## Creation Path Use the current agent's structured Linear issue tool. Tool names and exact field names vary, so inspect the active tool schema/help and map these intents to the available fields: - Set the `title`. - Assign it to the current Linear user. - Set its state to Todo. - Apply the chosen `agent-*` label. - Put the generated Markdown body in the issue description. - Set the parent issue when the user provided one. - Add dependency relations for blockers and blocked tickets. - Apply optional project, cycle, milestone, priority, estimate, and due date metadata only when requested or clearly inferable. Rules: - Use a blocked-by relation for "this work is blocked by X". - Use a blocking relation only when the user says the new ticket blocks another ticket. - If the tool cannot create relations during creation, create the issue first, then update it to add the parent and dependency relations. - If creating a parent and child tickets, create the parent without an `agent-*` label, then create labeled child tickets under that parent. ## Verification After creation: - Confirm the resulting issue identifier and URL. - Check that the issue has the intended assignee, state, `agent-*` label, repository line, parent, and relations. - If this Groundcrew repo or `crew` CLI is available, run `node --run crew -- status <ISSUE>` and report whether Groundcrew sees the ticket as ready for dispatch or why it will wait. Do not claim the ticket is eligible if verification fails. Report the missing field or blocking condition plainly.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.