gsd-discuss-phase
Implementation of gsd-discuss-phase command
816 repo starsObserved in 1 repos
Productivity
Productivity skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
history-insight
This skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").
809 repo starsObserved in 2 repos
Productivity
issue-reply
Use when drafting a concise GitHub issue or discussion reply for AtomUI based on repository state, bug analysis, requested behavior, workarounds, or maintainer follow-up questions.
809 repo starsObserved in 1 repos
Productivity
rpce-issue-creator
Draft, deduplicate, review, refine, or file maintainer-friendly GitHub issues for RepoPrompt CE from rough notes, investigation findings, or agent context. Use when a user or agent needs a clear RepoPrompt CE issue draft or explicitly requests issue filing.
808 repo starsObserved in 1 repos
Productivity
rpce-maintainer-guidance
Apply evidence-led RepoPrompt CE maintainership principles distilled from documented project guidance. Use when planning, scoping, implementing, reviewing, triaging, or sequencing RPCE changes; deciding whether work should be an investigation, issue, PR, or follow-up; checking compatibility, migrations, performance, observability, model defaults, or release risk; or asking how a proposed change fits the project's intended direction.
808 repo starsObserved in 1 repos
Productivity
weekly-pacing
Analyzes the user's upcoming or current work week using Work IQ signals (calendar, email volume, and semantic themes) and produces a visualized pacing report — classifying each day as Rest, Light, Focus, or Heavy based on meeting load, back-to-back density, communication volume, and available deep-work time. Designed for anxious users: leads with reassurance, names rest days first, surfaces the dominant themes of the week so it feels intentional, flags which days need focus, and ends with one concrete suggestion — never a list of warnings. Use when user asks to "show my week", "how does my week look", "is my week busy", "weekly pacing", "weekly workload", "do I have rest time", "which days are heavy", "where can I breathe this week", "workiq my week", "scan my week", "weekly rhythm check", "what's the shape of my week", or expresses anxiety about an upcoming week ("I'm dreading next week", "is this week going to be brutal"). Do NOT use for: daily briefings (use daily-briefing), single-meeting prep (use meeting-intel), scheduling new meetings (use schedule-meeting), or calendar cleanup actions (use calendar-management).
808 repo starsObserved in 1 repos
Productivity
pm-method-story-mapping
《User Story Mapping》方法论。把 Jeff Patton 的用户故事地图转化为可执行框架， 用于：把需求拆成能沟通的整体骨架、切出最小可用的发布切片、避免扁平待办清单。 每条规则标注原书章节，可追溯。 触发词：「User Story Mapping」「用户故事地图」「故事地图」「需求拆解」「MVP 切片」 「backbone」「walking skeleton」「怎么写用户故事」及"需求太碎/PRD 说不清全貌"类场景。
807 repo starsObserved in 1 repos
Productivity