Loading...
Loading...
Found 54 Skills
Persistent decision log that creates a read-write feedback loop: read previous decisions before starting work, respect or supersede them, and write new Y-statement records as you go. Activates during any task involving architectural, structural, or design decisions - choosing libraries, designing schemas, creating modules, making tradeoffs, selecting patterns. Also activates when DECISIONS.md already exists in the project. Do NOT activate for trivial changes like typos, renames, or formatting.
Build a 4-quadrant empathy map (Says, Thinks, Does, Feels) to synthesize user research into actionable insights. Use when you need to quickly capture and share user understanding across the team.
Create or update project charters from interactive or provided principle inputs, ensuring all dependent templates remain synchronized. Applicable to project management, specification formulation, charter maintenance, and team collaboration scenarios. Trigger words include "speckit constitution", "create charter", "update charter", "project charter", "formulate specification", "team charter"
Assign emails to teammates with context and track delegation status.
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Delivery Report Skill for Team Workflows (Phase 4). Generate PR Description (referencing plans/designs/verification items) and optionally sync with Jira Story.
Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.
Define a set of actionable design principles that guide decision-making and resolve trade-offs.
Clyde integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clyde data.
Use this skill when you need a standardized Claude Code workflow toolkit. It covers claudekit plugin installation, init-wizard scaffolding for rules/modes/hooks/MCP, and safe operating guidance for team adoption.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.