Results for “decision-board”

Condenses complex materials into a one-page executive decision memo with recommendation, evidence, tradeoffs, and next actions.

Prepare PRINCE2 Directing a Project gate briefs for project board decisions, including initiation authorization, stage authorization, exception decisions, and closure authorization.

Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.

Implements compliance with Turkey's Personal Data Protection Law (Kisisel Verilerin Korunmasi Kanunu, KVKK, Law No. 6698). Covers data controller obligations, data subject rights, VERBIS registration, cross-border transfer restrictions, Board decisions, and administrative fines. Keywords: KVKK, Turkey, VERBIS, data controller registry, Board decision, cross-border.

Be the CEO with strategic planning, board management, investor relations, financial modeling, crisis navigation, and executive decision-making.

Expert knowledge for Azure Boards development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing work items, queries/charts, GitHub links, Scrum boards/sprints, or WIQL-based integrations, and other Azure Boards related development tasks. Not for Azure DevOps (use azure-devops), Azure Test Plans (use azure-test-plans), Azure Pipelines (use azure-pipelines), Azure Repos (use azure-repos).

Plan a chunk of work too big for one agent session by putting it on a shared whiteboard — a map of investigation tickets on GitHub Issues — working them until nothing is left to decide, then snapshotting the board into a handoff artifact. Tickets needing nobody are worked back-to-back; the session stops when the human is the blocker. Use only when the user explicitly invokes whiteboard or asks to draw, work, run, or snapshot a whiteboard/map — not for ordinary planning requests.

Decide

Decide

Index and router for a C-level advisory bundle of 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use to explore the bundle, decide which advisor skill fits a question, or find entry points like the onboard interview, chief-of-staff routing, and board-meeting protocol.

Specify dashboards around decisions, audiences, questions, metrics, cuts, and refresh rhythm.

Convene a four-voice council of advisors to surface structured disagreement and tradeoffs for ambiguous decisions, go/no-go calls, and multi-path choices.

ADR Fleet

Convenes a council of specialized agents to debate important decisions, synthesizing independent perspectives into a structured recommendation and optional spec document.

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Guides users through structured decision-making with weighted scoring, criteria analysis, and clear recommendations, including quick and interview modes.

Structure a hard business decision — frame the choice, score options against weighted criteria, run a pre-mortem and stress-test, and produce a recommendation + decision record for any active brand

Generates a single-page Kanban board with four columns (To do, In progress, In review, Done), filter bar, and optional swimlanes.

Council

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc

Structure a decision into steelmanned, impact-weighted pros and cons - irreversible consequences flagged, the decisive unknown named, and a clear recommendation you can reject.

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

Design or revise a company's commercial policy governing discounts, approver thresholds, exception flows, and deal frameworks using data-backed matrices and linting tools.

Simulates a multi-perspective deliberation council to explore complex questions, decisions, or creative challenges from diverse thinking archetypes.

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Build board and investor update decks with structured narratives, metrics dashboards, and C-suite perspectives for board meetings, quarterly reviews, and fundraising.

Intercepts responses to let users choose the depth and token budget before answering, with heuristic token estimation and preset depth levels.