Loading...
Loading...
Found 72 Skills
Tinybird Code agent tools and prompts for working with Tinybird projects, datafiles, queries, deployments, and tests.
Show available Kata skills, displaying the usage guide, explaining skill reference, or when the user asks for help with Kata. Triggers include "help", "show skills", "list skills", "what skills", "kata skills", and "usage guide".
Creates task management documentation (docs/tasks/README.md + kanban_board.md). L2 Worker in ln-100-documents-pipeline. Sets up Linear integration and task tracking rules.
Updates ALL task types (implementation/refactoring/test). Compares IDEAL plan vs existing tasks, categorizes KEEP/UPDATE/OBSOLETE/CREATE, applies changes in Linear and kanban.
Brownian Ratchet progress gates for RPI workflow. Check, record, verify. Triggers: "check gate", "verify progress", "ratchet status".
Implement an existing PRD (`Type: feat`/`fix`/`chore`), update tests/checks, and mark completed PRD checklist items. Triggers: implement prd, build feature from prd, execute prd checklist.
Discussion entry when ideas are still vague — first conduct triage through 1-2 rounds of dialogue to determine which downstream process this discussion should eventually go to: if the idea is clear enough, proceed directly to feature-design; if the direction of a small requirement is set, continue the discussion within the feature and document it in `{slug}-brainstorm.md`; if a large requirement cannot fit into a single feature, hand it over to roadmap for decomposition. The role of AI is a thinking partner, not a recorder — dig out the real problem the user wants to solve, proactively evaluate when the user brings a solution, and propose alternative directions when necessary. Trigger scenarios: when the user says "I have an idea that's not clear yet", "Let's brainstorm first", "I want to do something but it's still vague", "Let's talk about this area", "The function direction is still undecided", or when the user comes with a specific solution but wants to hear other ideas first. Bugs (go to issue) and refactoring (go to refactor) are not handled here.
Track progress across sessions using SESSION.md with git checkpoints and concrete next actions. Converts IMPLEMENTATION_PHASES.md into trackable session state. Use when: resuming work after context clears, managing multi-phase implementations, or troubleshooting lost context.
Jira Cloud REST API via curl. Use this skill to create, update, search, and manage issues, projects, and workflows in Jira.
Syncs plan progress to a linked JIRA ticket. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep tickets in sync.
Analyze a GitHub issue and create a detailed technical specification
Rapid implementation for small, low-risk, well-defined changes. Use when the task is narrow in scope, has clear acceptance criteria, and can be completed safely without a formal multi-phase plan.