decision-interview
Interview a request owner about an unclear request or idea before work is planned. Use when the user says "interview me", "shape this request", or shares a vague request that needs decisions before a brief or issue. Do not use for questions that have a factual answer in the source.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- decision-interview
- description
- Interview a request owner about an unclear request or idea before work is planned. Use when the user says "interview me", "shape this request", or shares a vague request that needs decisions before a brief or issue. Do not use for questions that have a factual answer in the source.
03 SKILL.md 正文
Decision interview
Interview the request owner until each decision is made or assigned. Don't draft a brief or work item until the interview is done.
How to interview
- Read the attached source. Never ask what it already answers.
- Separate facts, assumptions, owner decisions, and missing information.
- Find the decision frontier: the decisions the owner can make now because the decisions they depend on are settled.
- Ask one numbered question at a time from the frontier. Wait for the answer.
- For each question, give your recommended answer and the tradeoff. The owner accepts, rejects, or revises it.
- Restate each decision with its reason and owner.
- When the frontier is settled, find the next one. Don't ask a question that depends on an open decision.
- Push back once on vague answers ("soon", "everyone", "clear"). Ask for a concrete example.
- Cover, skipping what is settled: target user and problem, outcome and non-goals, success and failure, boundaries and permissions, dependencies and ownership, approval.
When to stop
Stop when each branch has an accepted decision or a named open question with an owner. Don't invent decisions, owners, dates, or facts. Then write a summary with:
- Decisions, one line each, with the reason
- Open questions with an owner
- Next step
Ask the owner to correct the summary before you draft anything.
04 同仓库更多 Skills
release-notes
Write release notes or a CHANGELOG entry from a list of merged pull requests. Use when the user asks for release notes, a changelog entry, "what shipped", or a version summary, even if they don't name the format. Don't use for commit messages, PR descriptions, or marketing copy.
grill-me
Interview the user about a plan, idea, or design before any code is written. Use when the user says "grill me", "interview me", "stress-test this plan", or shares a rough idea and wants it pressure-tested. Do not use for questions that have a factual answer.
session-format-validator
Validate new or changed GitHub Copilot Train-the-Trainer session directories before they are added to the curriculum. Use this skill whenever a user creates, adds, updates, reviews, or asks whether a session under sessions/session-* follows the repository's repeatable format, including required materials, catalog metadata, navigation, and lab access or fallback guidance. Use it even when the user only asks to check a session README or lab.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
rvap-brand
Applies the RVAP (Real Value Acceleration Program) brand identity — colors, fonts, logo, and layout patterns — consistently to any GitHub Pages website. Use this skill whenever someone asks to brand, rebrand, apply RVAP/RVAS visual identity, make a site look RVAP, match the brand kit, or transform a GitHub Pages site's look and feel to match RVAP. Also trigger when the user shares an HTML/CSS/MkDocs site and says it should look consistent with other RVAP/RVAS materials, even if they don't explicitly say "brand".