Results for “team-critique”
28 skillsMore results
retro
Weekly engineering retrospective. (gstack)
0 · bundle
gh-review-requests
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.
845 · bundle
hewei-skill
贺炜(体育解说)认知与表达框架(压缩蒸馏):文学比喻嵌入赛况、克制激情、终场金句… 触发:足球诗人解说 等。非煽动球迷对立
9 · bundle
retro
Weekly engineering retrospective. (gstack)
0 · bundle
team-builder
Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Expert in team composition, personality balancing, collaboration ritual design, and skill creation for missing capabilities. Use for team design, role definition, skill gap identification. Activates on 'team building', 'team composition', 'skills needed', 'what skills'. NOT for general project management or solo work planning.
10
team-creator
Compose a provider-neutral AI team by tiering accessible models on cost-efficiency, capability, latency, and governance, then mapping the 8 processkit role archetypes onto catalog Roles + RoleSlots inside a chartering Scope. Use when bootstrapping a new project team, rotating after a provider change, or quarterly rebalancing. Triggers: "create my AI team", "compose a team", "rebalance the team", "review the team".
0 · bundle
retro
Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.
22.6k
ticket-writer
ticket-writer
0 · bundle
team-norms
Establish team norms for collaboration and communication. TRIGGERS - Use when user needs help with team-norms related tasks.
3
coaching-analyst
Coaching Analyst
0
grill-me
Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.
580 · bundle
iterate-retrospective
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.
0
retro
Weekly engineering retrospective. (gstack)
2 · bundle
team-outing
Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.
22
cx-criterion-library
Use to build and maintain a reusable bank of QA criteria as observable decision rules shared across scorecards. Trigger for "criterion library", "standardise our QA criteria", "write better rubric items", "was professional is too vague", versioning criteria across teams, or turning adjectives into pass/fail decision rules with examples.
1
session-critique
Runs an adversarial, decision-aware review of all session work before committing, checking decision adherence and code maintainability, and applies only user-authorized fixes.
0 · bundle
retrospective-insight-brief
Synthesize retrospectives into themes, root causes, decisions, and team improvements.
0
li-na-skill
李娜(网球 / 体育)认知与表达框架(压缩蒸馏):个性球员叙事、怼媒体金句、职业化独立 触发:法网、直率采访 等。非替本人编造
9 · bundle
load-testing
Most teams run one test — expected peak for ten minutes — and believe they have
2
team-outing
Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.
3
team-norms
Establish team norms for collaboration and communication. TRIGGERS - Use when user needs help with team-norms related tasks.
22
ingest
Team-Wiki Ingest
28
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
0
team-collaboration
Ownership models are usually inherited rather than chosen, and the inherited one
2
game-plan
Create game plans with strategy and tactics. TRIGGERS - Use when user needs help with game-plan related tasks.
3
retrospective
Generates a post-release blameless retrospective from project signals — synthesizing DORA-like metrics, WorkItem outcomes, session timeline, and drift deltas into a structured Artifact + LogEntry. Use at the end of a release cycle when asked to run a retro, "post-release review", "retrospective", or "post-mortem".
0 · bundle
ateam-design
ateam-design
0