Principles for creating evergreen notes - atomic, lasting insights that compound over time. Use when discussing note quality, what makes a good evergreen note, or the "only what was explored" principle. Tool-agnostic concepts that apply regardless of note-taking app.
Crea planes de implementación realistas para MVPs de 2-4 semanas. Define alcance mínimo, stack tecnológico, tareas priorizadas y cronograma. Úsalo después de validar una idea para planificar la construcción del producto mínimo viable.
Implement plugin tasks from plan with step iteration and progress tracking
複数のSkillsを連動させた一連のワークフローを設計するメタスキル。ユーザー確認ポイント、依存関係、エラー時のフォールバックを含む完全なワークフロー定義を生成。
扫描 topic 的 digests Claim Ledger，把“未核验 + 数字高影响”条目转成 tasks（核验待办）。
HAIOS Ground Cycle for loading architectural context before cognitive work. Use before plan-authoring, investigation, or implementation cycles.
A structured framework for dynamic and reflective problem-solving through sequential thoughts. Use when tackling complex, multi-step problems that require careful analysis, revision of assumptions, or exploration of alternative approaches. Ideal for algorithm optimization, architectural decisions, debugging complex issues, or any task where initial understanding may need to evolve.
This skill MUST be used when the user asks to "link issues", "relate issues", "mark as duplicate", "blocks issue", "is blocked by", "create issue link", "connect issues", or otherwise requests creating relationships between Jira issues.
Reusable workflow patterns for skills and agents including sequential checklists, conditional routing, validation loops, and progressive disclosure. Use when designing structured procedures.
체계적인 학습 계획 수립, 실행, 검증을 위한 학습 전용 워크플로우입니다. (퓨처 플래너의 학습 버전)
Break complex features into delegatable tasks with clear ownership and dependencies. Use for feature planning phase.
项目知识库管理器 - 将保险业务项目文档(数据分析、PPT报告、技术方案)转化为结构化、可迁移的知识资产。支持:(1)自动生成2类标准化模板(项目启动/技术方案);(2)从Markdown/代码仓库智能提取技术决策和可复用模式;(3)统一文档格式标准;(4)生成可跨项目复用的知识库。触发场景:用户要整理项目文档、创建知识库、生成项目模板、提取技术经验、标准化现有文档时使用。
Automated technical debt identification, tracking, and prioritization system
프로젝트 상태 점검 및 건강 진단. 상태, 점검, health, check, inspect 키워드에 자동 활성화.
Preserves session context when context window fills. Triggers at configurable thresholds (50%/75%). Captures objective, progress, technical details, decisions, blockers, and next steps.
Detects critical product, scope, data, risk, and success ambiguities in requirements or PRDs and expresses them as structured, decision-forcing clarification questions without proposing solutions or workflow actions.
Analyze completed parallel-executor session in fresh context and generate consolidation report. Use after all parallel stages complete. Spawns isolated subagent to analyze session history and create archive document.
Weekly review process for reflection and planning. Use when: "weekly review", "week summary", "Friday review", "what happened this week".
Guide development following Kent Beck's Test-Driven Development (TDD) using Red → Green → Refactor cycle. Use when writing tests first, implementing features with TDD, need to write failing tests, make tests pass, refactoring after tests pass, following red-green-refactor, fixing defects with tests, or practicing test-driven development methodology.
Evening task selection ceremony for maker work (discovery: requirements-clarity). Evaluate at requirements-clarity when user mentions shutdown ritual, evening ceremony, select for book, end of day selection, or tomorrow's tasks.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
