How work gets driven from an unformed idea to something tracked and built: exploring, pressure-testing, delegating implementation, ticketing, and capture. Invoke as /flow:<skill-name>. The scout skill requires the separately installed pathfinder and researcher agents; orchestrate requires implementer, pathfinder, researcher, structure-reviewer, and test-author.
Plugin flow from marketplace data-engineering-skills in victormacaubas/data-engineering-skills. Commands read from the repo's manifest — 8 days ago.
atlassian-cliCommand reference for the Atlassian CLI (`acli`) covering Jira work item reads and writes, Confluence reads, and the single-profile auth model. Use this whenever a task touches Jira or Confluence from the terminal - reading a ticket or its comments, searching with JQL, creating or editing a work ite
grill-mePressure-test and sharpen any change-shaped idea or artifact before implementation or commitment. Use when the user asks to be grilled, challenged, stress-tested, questioned, or pushed on an idea, proposal, design, spec, task list, ADR, PRD, BRD, plan, or similar artifact; clarify value, scope, term
orchestrateHave workers build a bounded plan instead of coding inline in the main session: use `test-author` to write the tests first, `implementer` to write code and `pathfinder` or `researcher` to close gaps that would otherwise require guesses. Use when a plan is ready to build - "implement the plan", "appl
scoutThink through an undecided problem as a conversation, sending `pathfinder` and `researcher` to do the reading so the sources stay out of the main context. Use whenever the shape of the work is still open - "let's explore X", "help me think through this", "brainstorm this with me", "I'm considering A
stashPark content into the Obsidian vault's inbox/ folder raw — no synthesizing, no placement — so /process-inbox can file it later. Use when the user says "stash this", "save this conversation", "park this for later", "dump the session", or wants to offload content before running out of context. Handles
write-ticketWrite tickets and comments in plain, human-sounding language using the Atlassian CLI (`acli`). Use when the user wants to create a ticket ("file a ticket", "open an issue", "track this as a task") OR respond to an existing ticket ("respond to PROJ-123", "update the ticket", "comment on this", "post
How code gets written and checked: architectural baselines, Python standards, and the defect and structure reviews that gate a finished change. Invoke as /craft:<skill-name>. The architecture-baseline skill requires the separately installed researcher agent.
4 skills
The warehouse surface: canonical SQL standards for trustworthy analytics, and Snowflake ACCOUNT_USAGE auditing for masking, row access, classification, tags, grants, logins, and query history. Invoke as /data:<skill-name>.
2 skills
Claude Code only. Optional. Denies the implementer agent file edits on the test tree and the test-author agent file edits on production code. Without it, both agents are bounded by their instructions only.
Claude Code only. Shows the SQL that the main session and its subagents run through the snowflake-raw MCP server in a pane, grouped by agent. Requires the snowflake-raw MCP server.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.