菜单
Facilitates structured single-persona or multi-persona consultation for strategy, product, engineering, operations, and risk decisions. Use when the user requests a council, multiple perspectives, persona advice, tradeoff analysis, or iterative clarification and debate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Personal daily briefing assistant. Pulls the last 24 hours of email and calendar from Outlook, summarizes today's schedule, surfaces open action items, and proposes focus blocks. Use when user says "daily briefing", "morning briefing", "daily standup prep", or invokes /daily-briefing.
Draft a customer-facing release note for a Jira ticket by gathering the ticket context (summary, description, type, fix version, comments) and any linked GitLab merge requests / code changes, then synthesizing a clear, audience- appropriate release note. Runs a clarity-council quality pass over the draft. Read-only by default; the user may opt in at the end to publish the note as a Jira comment (or into a Release Notes field if one exists). Use when user says "draft release notes", "write a release note", "release note for [TICKET-KEY]", "what changed in this ticket", or invokes /issue-draft-release-notes with a ticket key.
Generate a per-team standup markdown report by gathering activity over the last N days from Jira, GitLab, Confluence, and a local Git repo. Maps activity to team members from a roster CSV, renders a Mermaid kanban + randomized talking order, captures a `daily`-tagged sprint snapshot, and runs a clarity-council (infographics-expert burndown chart + statistics-expert forecast + scrum-master suggestions) for sprint pulse. Writes one file per team into the Obsidian vault. Use when the user says "daily standup prep", "standup report", "generate standup", "scrum prep", or invokes /daily-standup-prep.
Morning kickoff wrapper that runs sprint-snapshot (daily tag), daily-standup-prep (with sprint burndown), and daily-briefing (report only — no focus-block suggestions) in order. Re-runs idempotently — existing same-day artifacts are overwritten in place. Use when user says "good morning", "morning routine", "kick off my day", "start my day", or invokes /good-morning.
Capture a point-in-time snapshot of a scrum team's current sprint board from Jira and render it into the Obsidian vault as (1) an Obsidian Canvas with sprint overview, team workload, kanban columns, and issue cards, (2) a companion markdown summary, and (3) an append-only JSONL trend log. Auto-detects sprint phase (start / week 1 / week 2 / week 3 / end) from today's date. Supports `--as-of <date>` for historical snapshots. Reuses obsidian-canvas / obsidian-vault / obsidian-markdown for vault writes and follows the issue-* skills' Jira context-gathering patterns. Use when user says "sprint snapshot", "snapshot the sprint", "capture sprint state", "sprint planner", "scrum board snapshot", or invokes /sprint-snapshot.
Safely rebase the current branch onto its upstream target (baseline, main, or master). Auto-resolves simple merge conflicts (version bumps, changelogs). Prompts for complex ones. Use when user says "rebase", "rebase branch", "rebase onto main", "update my branch", "sync with baseline", "catch up with main", or invokes /branch-rebase.
| name | clarity-council |
| description | Facilitates structured single-persona or multi-persona consultation for strategy, product, engineering, operations, and risk decisions. Use when the user requests a council, multiple perspectives, persona advice, tradeoff analysis, or iterative clarification and debate. |
| related-agents | ["council-single-persona","council-multi-persona","council-iterative"] |
| related-skills | ["grill-me","idea-generate"] |
| loop-eligible | false |
| recurrence-hint | on-demand |
This skill routes to three specialized agents in the agents/00-council/ folder. Use the appropriate agent based on your decision-making need.
Use this system when you need any of the following:
Do not use for pure factual lookup with no decision component.
Agent: council-single-persona
When: You need focused advice from one expert (quick, 10–15 min)
Example: "As a senior-architect, should we migrate to microservices?"
Agent: council-multi-persona
When: A decision needs multiple viewpoints synthesized (20–30 min)
Example: "Convene a council on Kubernetes adoption."
Agent: council-iterative
When: You need multi-turn iteration with clarifications (30–60 min, 3–5 turns)
Example: "Run a council on team restructuring. I'll iterate."
Simply invoke the appropriate agent directly:
/council-single-persona
As a product-owner, should we ship this quarter?
/council-multi-persona
Convene a council on whether to adopt TypeScript.
/council-iterative
Run a council on payment processor selection. I'll iterate.
See the full documentation at agents/00-council/README.md and agents/00-council/INDEX.md.
Use these structures exactly unless the user asks for a different format.
summary: <short answer>
advice:
- <point>
assumptions:
- <assumption>
questions:
- <question>
next_steps:
- <action>
confidence: <low|medium|high>
responses:
- persona: <name>
summary: <short answer>
advice:
- <point>
assumptions:
- <assumption>
questions:
- <question>
next_steps:
- <action>
confidence: <low|medium|high>
synthesis:
agreements:
- <point>
conflicts:
- <point>
risks_tradeoffs:
- <point>
next_steps:
- <action>
status: <needs_clarification|in_progress|completed>
message: <short user-facing response>
nextAction: <what is needed next>
output:
<single-persona or multi-persona structure>
state:
sessionId: <id>
turn: <number>
history:
- <compact turn summary>
Agent documentation:
agents/00-council/README.md — Comprehensive guide to all agentsagents/00-council/INDEX.md — Quick navigation and decision treeagents/00-council/council-single-persona.md — Single expert agentagents/00-council/council-multi-persona.md — Multi-expert synthesis agentagents/00-council/council-iterative.md — Iterative decision agentPersona library:
Before finalizing a response: