メニュー
Compose structured backlog ticket bodies using the Why/Role/Integration/Edges/Touch-points template. Use when user says "ticket authoring", "compose", "write a ticket body", or "author a backlog item". Two subcommands: interview (guided prompts) and compose (autonomous, context-driven).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Structured feature development lifecycle with phases for research, specification, planning, implementation, review, and completion. Use when user says "/cortex-core:lifecycle", "start a lifecycle", "lifecycle research/specify/plan/implement/review/complete", "start a feature lifecycle", or wants to build a non-trivial feature with structured phases.
Development entry point that analyzes requests and routes to the appropriate workflow. Use when user says "/cortex-core:dev", "what should I work on", "start working on", "dev hub", "where do I start", "next task", "what's next", or describes a feature without naming a specific skill.
Prepare a backlog item for execution by running it through Clarify → Research → Spec. Use when user says "/cortex-core:refine", "refine backlog item", "prepare for overnight", or "prepare feature for execution". Produces cortex/lifecycle/{slug}/research.md and cortex/lifecycle/{slug}/spec.md, then sets status:refined on the backlog item.
Parallel research orchestrator. Use when the user says "/cortex-core:research", "research this topic", "investigate this feature", or when /cortex-core:refine delegates its research phase. Dispatches 3–10 parallel agents across independent angles, synthesizes into research.md or conversation output.
Create git commits with consistent, well-formatted messages. Use when user says "commit", "/cortex-core:commit", "make a commit", "commit these changes", or asks to save/checkpoint their work as a git commit.
Guide the user through the morning report after an overnight session. Walks Executive Summary and report sections, collects answers to deferred questions, advances completed lifecycles to Complete, and auto-closes backlog tickets. Use when the user says "/morning-review", "morning review", or "what happened overnight".
| name | backlog-author |
| description | Compose a structured backlog ticket body from a context block, using the Why/Role/Integration/Edges/Touch-points template. Use when user says "compose a ticket", "write a ticket body", or "author a backlog item". |
| argument-hint | compose <context-block> |
Compose one ticket body per invocation from the provided context block (a caller with N pieces invokes N times). Emit only the markdown body to stdout — frontmatter belongs to cortex-create-backlog-item --body.
Emit the five-section markdown body to stdout, sections in order — ## Why, ## Role, ## Integration, ## Edges, ## Touch points — all required except ## Touch points. Prose only: no path:line or §N citations and no fenced code blocks outside ## Touch points, where those forms are the norm.
## Why — the problem in symptom-voice: what is broken, missing, or degraded, in observable terms. Not the solution. Omit this section when it collapses to a restatement of Role's lead.## Role — the job this piece does once the ticket lands that nothing did before (arc42 Responsibility), not its mechanism.## Integration — how it connects inbound and outbound, naming Interface surfaces by name (e.g. "the phase-transition contract").## Edges — structural constraints and boundary conditions: what breaks if an upstream contract changes shape, what this must not do, which non-goals keep scope tight. Each bullet names a contract surface or a non-goal.## Touch points — implementation locations: file paths with line numbers, section indices, code excerpts. Omit when none are known.If an ## Edges bullet needs a path:line to express its constraint, the path:line moves to ## Touch points and a structural summary stays in ## Edges.