brandon-fryslie
Publisher on askill
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated c...
Silently capture workflow observations to retro log when you notice repeated issues, user frustration, or process inefficiencies. Use when you observe patterns that could improve future work.
Use the bd (beads) CLI for persistent issue tracking across sessions. Invoke when work spans multiple sessions, has complex dependencies, or requires context preservation across compaction cycles. Pro...
Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations
Use when asked to send or read Slack messages, check Slack channels, test Slack integrations, or interact with a Slack workspace from the command line.
Remove what has served its purpose and now obscures. Finds dead code, orphaned functions, scaffolding that outlived its use, and vestigial features. Uses distillation to know what to preserve. Outputs...
Tracks complex, multi-session work using the Beads issue tracker and dependency graphs, and provides persistent memory that survives conversation compaction. Use when work spans multiple sessions, has...
Forensic test coverage audit - exhaustive detection of complexity sources and assessment of whether tests exist at the right level. Use when reviewing test quality, identifying testing gaps, or auditi...
Code review and quality assessment. Use when user wants to review a PR, recent changes, or specific code.
Bug fix workflow with verification. Use when user wants to fix a known bug or issue.
External/market research - competitive landscape, demand signals, alternatives. Use when user asks about competitors, market demand, or external approaches.
Research a problem or question through iterative exploration. Loops researcher->evaluator until sufficient, then auto-selects recommendation. Output feeds into /plan. Entry point for /do:research comm...
Audit alignment across strategy, architecture, plans, and implementation. Ensures planning documents remain effective and aligned over time. Supports quick, medium, and thorough intensity levels.
Comprehensive technical audit checklists for architecture, design, efficiency, and domain-specific analysis. Use when project-evaluator runs in audit mode.
Write tests first, then implement. TDD workflow with TestLoop and ImplementLoop. Entry point for /do-more:tdd command.
Analyze structural rigidity in codebase. Identifies high-coupling areas, dependency cycles, and recommends boundary insertions. Use when module changes cause cascading failures.
Showing 18 of 23