Loading...
Loading...
Found 5 Skills
AI-Native Issue-Driven development workflow. From GitHub Issue to merged PR: parse issue, explore codebase, design technical plan, execute with agent team, create PR, and cleanup. Use when a user wants to implement a GitHub Issue end-to-end: `/issue-flow #123` or `/issue-flow` to pick from open issues.
This skill should be used when the user has a completed implementation plan (plan.md) and is ready to execute the tasks defined therein. Actively uses Agent Teams or subagents to execute batches of independent tasks in parallel, following BDD/TDD principles.
Traditional development workflow skill for product requirement intake, engineering research, technical planning, task breakdown, implementation, testing, bugfix loop, and engineering review. Use when a user wants to run or continue a structured software delivery workflow that mirrors real product-development collaboration.
This skill is activated when the user's team faces execution problems—such as failing to meet OKRs, constantly changing plans, and passive team response to instructions. Typical trigger signals: Goals are set but execution deviates, plans can't keep up with changes, and the team only completes assigned tasks without proactive thinking. Non-trigger scenarios: Execution is good and only needs fine-tuning, the problem lies at the strategic level rather than the execution level, and individual work does not require a team execution framework. Difference from the "Strategy-Tactics Dialectics" skill: This skill solves "how to balance the three dimensions of execution" (execution layer), while the latter solves "dialectical design of offensive and defensive levels" (strategy layer).
World-class OKR coaching and sparring partner that provides sharp, practical criticism for OKR drafts. Use when creating, reviewing, or refining OKRs to ensure strategic alignment, measurability, and executability.