todo-domain-expert
Provides domain knowledge and rules for Todo task management systems.
Provides domain knowledge and rules for Todo task management systems.
実装計画の続きから作業を再開。doc/plans/ の計画ファイルを読み込み、「8. 現在の進捗」セクションから次のタスクを把握して実装を継続する。セッション開始時やコンテキスト圧縮後の復帰に使用。トリガー - 「計画を再開」「続きから」「resume」「plan再開」
/orchestrate 커맨드의 상세 워크플로우 가이드. 모든 Phase 처리 및 sub-agent spawn 전략
Use when creating or updating tickets. Covers ticket writing best practices, what to include, and what to avoid.
NetGraph scenario DSL for defining network topologies, traffic demands, failure policies, and analysis workflows in YAML. Use when: creating or editing .yaml/.yml network scenarios, defining nodes/links/groups, writing link rules with patterns, configuring selectors or blueprints, setting up traffic demands or failure policies, running scenarios and interpreting results, debugging DSL syntax or validation errors, or asking about NetGraph scenario structure.
Use this skill group when the user wants to "generate a report", "executive summary", "technical alert", "weekly briefing", or mentions reporting, leadership briefings, SOC alerts, or documentation. This skill group generates formatted threat intelligence reports for different audiences including executives, technical teams, and compliance purposes.
SAP ECC expert for automotive manufacturing operations. Covers Materials Management (MM), Production Planning (PP), Sales & Distribution (SD), Quality Management (QM), Plant Maintenance (PM), and Finance/Controlling (FI/CO). USE WHEN user says 'SAP', 'ECC', 'transaction code', 't-code', 'MRP', 'purchase order', 'production order', 'goods receipt', 'goods issue', 'material master', 'BOM', 'routing', 'work center', or needs help with SAP processes. Integrates with AutomotiveManufacturing and SupplyChain skills.
会議の文字起こしから要約・アクションアイテム・決定事項を抽出する。要約、サマリー、アクションアイテム、議事録作成時に使用。
Use when executing implementation plans with independent tasks in the current session
Create flexible boundaries for projects - not rules or requirements, but bumpers that guide without constraining. Use when starting projects, when feeling overwhelmed by possibilities, or when needing structure without suffocation.
Orchestrate KB development workflow from request to completion. Coordinates skills in sequence: kb → plan → test → validate → complete → reflect → inbox. WORKFLOW: 1. LOOKUP - /pmc:kb (check existing PRDs, patterns, code maps) 2. PLAN - /pmc:plan + /pmc:plan-validation + /pmc:lint-kb 3. IMPLEMENT - /pmc:test (TDD cycle: RED → GREEN → REFACTOR) 4. VALIDATE - /pmc:validate + /pmc:ticket-status 5. COMPLETE - /pmc:complete (write 5-final.md, commit) 6. REFLECT - /pmc:reflect + /pmc:lint-kb 7. INBOX - /pmc:inbox (process pending items) Use when: - User says "implement", "build", "develop", "work on" - Starting new feature or phase work - Need guided workflow from start to finish - User says "dev workflow", "full cycle"
PCE (Process-Context Engine) のコンテキスト圧縮スキル。長期タスクの履歴を要約・圧縮し、セッション継続を可能にする。 トリガー条件: - セッションが長くなった時 - コンテキストウィンドウが逼迫した時 - 「ここまでをまとめて」 - 「ノートを作成して」 - 複数セッションにまたがる作業の時 - 「次回のために記録して」
Reference and maintain the project's technical stack including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across the project. Use this skill when making technology choices, adding new dependencies, configuring frameworks, or ensuring consistency with existing stack decisions. When setting up new features that need to align with the project's chosen technologies. When documenting or updating the tech stack. This skill applies when working with any technology-specific configuration, framework setup, or when making architectural decisions about tools and libraries.
[70] CLOSE. Manage task lifecycle with correct statuses and no duplicates. Ensure each task has one status, artifacts match claims, and no task appears in multiple places. Use when managing task lists, updating progress, or ensuring task tracking integrity across systems.
Creates or updates feature implementation plan documents in doc/plan. Use when planning a new software feature, refining feature scope/name, tracking TODO/DONE progress, or marking a plan as achieved.
Determines project type from context to configure analysis thresholds. Checks prompt, scans documents, or asks user if type cannot be inferred. Outputs project_type for use by python-plan-optimization skill.
skill__spec__set `spec set <yyyy-mm-dd> <taskName>` [SET] Switch to existing CODE_SPEC.
Creates structured implementation plans from feature requirements. Use when planning new features, multi-phase projects, or when the user asks for an implementation plan, build plan, or development roadmap.
Use when determining how fast or slow motion should be—pacing action sequences, dramatic pauses, comedic beats, or any situation where the duration of movement matters.
Systematic todo management approach. Analyze task clarity before adding; ask for details when needed to ensure actionability. Uses Obsidian's todo.md with three regions: Important (重要), Todo, Finish (完成). Trigger when user says "添加任务", "新任务", "记录待办", "管理任务" or needs task reasoning, priority judgment, or task breakdown.
Use when executing implementation plans with independent tasks in the current session