project-management
1
lno-time-management-framework
Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (<1x) to escape the trap of treating all tasks as equally important. Apply perfectionism only to L tasks.
Coowoolf
business
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
sales-marketing
1
systematic-planning
Systematic feature planning workflow - use when starting complex features requiring structured approach
ashchupliak
business
project-management
1
plan-on-md
A skill to save plans to local Markdown after creating them in plan mode
uuta
business
project-management
1
pre-mortem-framework
Instead of waiting for a post-mortem after failure, imagine the project has already failed spectacularly and work backward to uncover hidden risks. Use before kicking off any major initiative, product launch, or high-stakes project.
Coowoolf
business
project-management
1
phase-planning
Generate 5-phase implementation plan with validation gates and resource allocation. Adapts phase count and timeline based on complexity score. Includes validation gates between phases. Use when: planning implementation, need structured timeline, want validation checkpoints.
krzemienski
business
project-management
1
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Vpr99
business
project-management
1
improve-tbta
Systematically work through TBTA features using the 6-stage STAGES.md workflow. Use when user wants to improve TBTA features, work on TBTA, or continue TBTA feature work.
authenticwalk
business
project-management
1
phase-05-development-execution
Execute development in sprints with continuous quality. Sprint planning, code development, code reviews, security in development (shift left), unit testing, integration, and documentation.
Harery
business
project-management
1
project-analysis
A specialist skill that analyses a codebase to understand its structure, dependencies, and architecture. This skill should be used at the start of a new project or when onboarding to an existing codebase.
nicholasgriffintn
business
project-management
1
honest-reflections
Systematic gap analysis for claimed vs actual work completion. Uses 100+ sequential thoughts to identify assumptions, partial completions, missing components, and rationalization patterns. Validates completion claims against original plans, detects scope deviations, reveals quality gaps. Essential for self-assessment before declaring work complete. Use when: claiming completion, final reviews, quality audits, detecting rationalization patterns in own work.
krzemienski
business
project-management
1
executing-plans
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
seanGSISG
business
project-management
1
openspec-to-beads
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.
lucastamoios
business
project-management
1
spec-workflow
仕様駆動開発（SDD）ワークフローを自動発動で強制。Subtask開始時にAC確認、TDD実行、完了時にACチェックを実施。スコープ外実装を禁止。Use when implementing features, creating new functionality, or when "実装して", "作成して", "開発して" keywords appear.
Sn005
business
project-management
1
writing-plans
当有多步骤任务的规格或需求时使用，在动代码之前。编写全面的实施计划，假设工程师对代码库零上下文。Use when you have a spec or requirements for a multi-step task, before touching code. Write comprehensive implementation plans.
hxk622
business
sales-marketing
1
brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation through collaborative dialogue.
rbergman
business
project-management
1
compound-engineering
Compound Engineering methodology - Plan→Work→Review→Compound loop where each unit of work makes subsequent work easier. Use when implementing features, fixing bugs, or any development work.
5dlabs
business
project-management
1
issue-lister
オープン Issue の一覧を優先順位付きで表示する。「Issue 一覧」「Issue リスト」「オープン Issue」「Issue を見せて」「チケット一覧」「未解決 Issue」「Issue 確認」などで起動。優先度順にソートして表示。
shiiman
business
sales-marketing
1
sprint-plan
Create comprehensive sprint plans by intelligently grouping estimated user stories based on velocity, dependencies, priorities, and risk. This skill should be used during sprint planning ceremonies to transform backlog into actionable sprint commitments.
adolfoaranaes12
business
project-management
1
session-discipline
Enforce session-first workflow (plan → implement → verify → document). Use whenever starting non-trivial work, debugging >15 minutes, or doing cross-cutting changes.
metabench
business
project-management
1
build-one-to-throw-away
Apply throwaway prototyping methodology when exploring new concepts, unfamiliar technology, or unclear requirements. Build fast, learn deeply, then rebuild properly. Use for feasibility studies, proof-of-concepts, and learning exercises.
jzallen
business
project-management
1
analyzing-specifications
Use when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag
krzemienski
business
project-management
1
risk-profile
Assess implementation risks using Probability × Impact (P×I) scoring methodology across 6 categories (Technical, Security, Performance, Data, Business, Operational). Scores risks (P×I: 1-9), develops mitigations for high-risk items (score ≥6), and prioritizes test scenarios (P0/P1/P2). Use before implementation or during quality review to identify and mitigate potential issues.
adolfoaranaes12
business