skill_fixture

Name: skill_fixture
Author: andrewstellman

69stars7forks

How to install skill_fixture?

andrewstellman/quality-playbook/skill_fixture

$npx -y skills add andrewstellman/quality-playbook --skill skill_fixture

Installs into the current project.

Summary

A pure-prose AI skill that helps teams prepare for and run daily standup meetings. This SKILL.md fixture is used by bin/tests/test_classify_project.py as a known-Skill target for the v1.5.3 project-type classifier: SKILL.md at fixture root, no substantial code, prose word count

Files · 1

View on GitHub

SKILL.md

1	# Daily Standup Coach (Skill classifier fixture)
2
3	A pure-prose AI skill that helps teams prepare for and run daily standup
4	meetings. This SKILL.md fixture is used by `bin/tests/test_classify_project.py`
5	as a known-Skill target for the v1.5.3 project-type classifier: SKILL.md at
6	fixture root, no substantial code, prose word count substantially exceeds
7	code line count.
8
9	The fixture is a synthetic skill, not a real one in production use; its
10	content is realistic enough to exercise the classifier but should not be
11	mistaken for a deployable skill.
12
13	## When to use this skill
14
15	The skill activates when an operator asks for help running a daily standup
16	meeting. Triggers include phrases like "help me run standup," "review my
17	standup notes," "draft talking points for tomorrow's standup," or "summarize
18	this week's standups." It can also be invoked as part of a larger sprint
19	ceremony orchestration where standup is one of several meetings the operator
20	needs to facilitate.
21
22	The skill does not activate for retrospectives, sprint planning, refinement
23	sessions, or other agile ceremonies. Those meetings have different shapes
24	and different anti-patterns and would need their own skills. If an operator
25	asks the skill to handle a non-standup meeting, the skill politely declines
26	and points at the appropriate alternative tool, if one exists, or suggests
27	the operator use a general-purpose meeting facilitator.
28
29	## What this skill produces
30
31	For each invocation the skill produces three artifacts. The first is a
32	concise meeting agenda: who is presenting, in what order, with how much
33	time each. The agenda follows the round-robin pattern that most teams
34	default to, but the skill will reorder if the operator has flagged that a
35	specific blocker should be discussed first. The second artifact is a set of
36	prompts the operator can use to keep the meeting on track: when to redirect
37	a tangent, when to move someone to "parking lot," when to escalate a
38	recurring blocker. The third artifact is a brief written summary of the
39	meeting that can be posted to a shared channel after the meeting concludes.
40
41	The artifacts are written incrementally as the skill processes the
42	operator's input. The agenda lands first because most operators want to
43	review it before the meeting; the prompts land second because they're
44	needed during the meeting; the summary template lands last because it's
45	populated post-meeting from the operator's notes.
46
47	## Phase 1 — Pre-meeting preparation
48
49	Phase 1 runs in the time window between the operator deciding to use the
50	skill and the standup meeting starting. The skill reads any context the
51	operator provides — last week's notes, the team's current sprint goals,
52	known blockers — and produces a draft agenda.
53
54	Phase 1's output is `agenda.md` in the operator's working directory. The
55	file has three sections: roster (who is expected to attend, in presentation
56	order), focus areas (sprint goals being discussed this week), and parking
57	lot (topics that came up but should be deferred). Each section is brief —
58	the agenda is meant to fit on one screen so the operator can keep it open
59	during the meeting.
60
61	The operator can edit the agenda before the meeting. The skill respects
62	operator edits and uses the edited agenda as the basis for the next phase
63	rather than regenerating from scratch.
64
65	If the operator hasn't provided any context, Phase 1 produces a skeleton
66	agenda with placeholders the operator fills in. This is the most common
67	case for first-time use of the skill — the operator hasn't yet trained the
68	skill on the team's specific dynamics.
69
70	## Phase 2 — In-meeting facilitation
71
72	Phase 2 runs during the standup meeting itself. The operator is presumably
73	busy facilitating, so the skill operates in low-touch mode: it watches a
74	shared notes document the operator updates as the meeting progresses, and
75	emits short prompts when it detects patterns that need redirection.
76
77	Patterns the skill watches for include: someone has been talking longer
78	than their allotted time; the same blocker has come up across multiple
79	recent standups; a topic is drifting into deep-dive territory and should be
80	moved to a follow-up meeting; the team is reporting all-green on a goal
81	that other signals suggest is at risk.
82
83	When the skill detects one of these patterns, it emits a prompt as a
84	comment in the shared notes. The prompt is brief and actionable: not "this
85	discussion seems to be drifting," but rather "consider parking this for a
86	follow-up; @alice and @bob can sync after standup." The operator can ignore
87	the prompt, apply it, or modify it.
88
89	Phase 2's output is the cumulative set of prompts emitted during the
90	meeting. They live in `meeting_prompts.md` and are timestamped so the
91	operator can correlate them with the meeting recording if one exists.
92
93	## Phase 3 — Post-meeting summary
94
95	Phase 3 runs after the standup meeting concludes. The operator typically
96	hands the skill the raw notes from the meeting plus any audio transcript
97	the team's recording tool produced. The skill produc

People who liked this also viewed

6 picks

Type

skill_fixture

69stars7forks

View on GitHub

How to install skill_fixture?

andrewstellman/quality-playbook/skill_fixture

$npx -y skills add andrewstellman/quality-playbook --skill skill_fixture

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Daily Standup Coach (Skill classifier fixture)
2
3	A pure-prose AI skill that helps teams prepare for and run daily standup
4	meetings. This SKILL.md fixture is used by `bin/tests/test_classify_project.py`
5	as a known-Skill target for the v1.5.3 project-type classifier: SKILL.md at
6	fixture root, no substantial code, prose word count substantially exceeds
7	code line count.
8
9	The fixture is a synthetic skill, not a real one in production use; its
10	content is realistic enough to exercise the classifier but should not be
11	mistaken for a deployable skill.
12
13	## When to use this skill
14
15	The skill activates when an operator asks for help running a daily standup
16	meeting. Triggers include phrases like "help me run standup," "review my
17	standup notes," "draft talking points for tomorrow's standup," or "summarize
18	this week's standups." It can also be invoked as part of a larger sprint
19	ceremony orchestration where standup is one of several meetings the operator
20	needs to facilitate.
21
22	The skill does not activate for retrospectives, sprint planning, refinement
23	sessions, or other agile ceremonies. Those meetings have different shapes
24	and different anti-patterns and would need their own skills. If an operator
25	asks the skill to handle a non-standup meeting, the skill politely declines
26	and points at the appropriate alternative tool, if one exists, or suggests
27	the operator use a general-purpose meeting facilitator.
28
29	## What this skill produces
30
31	For each invocation the skill produces three artifacts. The first is a
32	concise meeting agenda: who is presenting, in what order, with how much
33	time each. The agenda follows the round-robin pattern that most teams
34	default to, but the skill will reorder if the operator has flagged that a
35	specific blocker should be discussed first. The second artifact is a set of
36	prompts the operator can use to keep the meeting on track: when to redirect
37	a tangent, when to move someone to "parking lot," when to escalate a
38	recurring blocker. The third artifact is a brief written summary of the
39	meeting that can be posted to a shared channel after the meeting concludes.
40
41	The artifacts are written incrementally as the skill processes the
42	operator's input. The agenda lands first because most operators want to
43	review it before the meeting; the prompts land second because they're
44	needed during the meeting; the summary template lands last because it's
45	populated post-meeting from the operator's notes.
46
47	## Phase 1 — Pre-meeting preparation
48
49	Phase 1 runs in the time window between the operator deciding to use the
50	skill and the standup meeting starting. The skill reads any context the
51	operator provides — last week's notes, the team's current sprint goals,
52	known blockers — and produces a draft agenda.
53
54	Phase 1's output is `agenda.md` in the operator's working directory. The
55	file has three sections: roster (who is expected to attend, in presentation
56	order), focus areas (sprint goals being discussed this week), and parking
57	lot (topics that came up but should be deferred). Each section is brief —
58	the agenda is meant to fit on one screen so the operator can keep it open
59	during the meeting.
60
61	The operator can edit the agenda before the meeting. The skill respects
62	operator edits and uses the edited agenda as the basis for the next phase
63	rather than regenerating from scratch.
64
65	If the operator hasn't provided any context, Phase 1 produces a skeleton
66	agenda with placeholders the operator fills in. This is the most common
67	case for first-time use of the skill — the operator hasn't yet trained the
68	skill on the team's specific dynamics.
69
70	## Phase 2 — In-meeting facilitation
71
72	Phase 2 runs during the standup meeting itself. The operator is presumably
73	busy facilitating, so the skill operates in low-touch mode: it watches a
74	shared notes document the operator updates as the meeting progresses, and
75	emits short prompts when it detects patterns that need redirection.
76
77	Patterns the skill watches for include: someone has been talking longer
78	than their allotted time; the same blocker has come up across multiple
79	recent standups; a topic is drifting into deep-dive territory and should be
80	moved to a follow-up meeting; the team is reporting all-green on a goal
81	that other signals suggest is at risk.
82
83	When the skill detects one of these patterns, it emits a prompt as a
84	comment in the shared notes. The prompt is brief and actionable: not "this
85	discussion seems to be drifting," but rather "consider parking this for a
86	follow-up; @alice and @bob can sync after standup." The operator can ignore
87	the prompt, apply it, or modify it.
88
89	Phase 2's output is the cumulative set of prompts emitted during the
90	meeting. They live in `meeting_prompts.md` and are timestamped so the
91	operator can correlate them with the meeting recording if one exists.
92
93	## Phase 3 — Post-meeting summary
94
95	Phase 3 runs after the standup meeting concludes. The operator typically
96	hands the skill the raw notes from the meeting plus any audio transcript
97	the team's recording tool produced. The skill produc

People who liked this also viewed

6 picks

Type