Complete story implementation workflow from start to finish. Use when implementing user stories, features, or epics. Handles validation, development (with optional parallel execution), QA review, issue resolution, and PR creation. Can implement single stories, multiple stories, or entire epics in parallel.
Start working on a tracked issue. Use when beginning work on an issue, logging progress, or managing issue workflow.
Standard 5-phase workflow for most development tasks - bugs, small features, refactors (30-60 min)
This skill should be used when the user asks to "collect GitHub activity", "generate GitHub report", "show my PRs and commits", "what did I work on in GitHub", or requests activity summaries from GitHub for specific date ranges. Provides workflow for collecting issues, PRs, and commits via GitHub CLI.
Structured peer review for analytical work. Use when reviewing teammates' analysis, providing constructive feedback, or establishing analysis quality standards.
Use when you have a written implementation plan to execute with review checkpoints
進捗報告書を作成するスキル。開発案件の進捗状況を、技術的背景を持たないステークホルダーにもわかりやすく伝える報告書を生成。「進捗報告を作って」「ステータスレポートを書いて」「報告書を作成して」などのリクエストに使用。
Scans and reports all planning-related components across marketplace bundles
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의 - You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Break down high-level requirements into concrete implementation plans.
Complete data science research workflow for Jupyter notebooks covering CRISP-DM methodology from data loading through model validation, with MLflow experiment tracking integration, phase-based workflow guidance (Exploration, Systematic Experimentation, Analysis, Documentation), and skill integration points. Use when working on FYP data science projects requiring systematic data preprocessing, EDA, feature engineering, modeling, statistical validation, experiment tracking, or needing guidance on what to work on at each project phase. Includes MLflow setup for tracking 30+ experiment runs, weekly work planning for 10-week FYP timeline, and clear decision framework for when to use which skill (fyp-jupyter, crossvit-covid19-fyp, fyp-statistical-validator, tar-umt-fyp-rds, tar-umt-academic-writing).
规划修订导航。触发：用户通知"analysis-agent已分析完成"或需要plan-agent查看analysis-agent复审结果并修订预定清单时使用；评估analysis-agent分析结果并修订draft-plan.md。
Agentic Scrum Master for software development projects. Use this skill when acting as Scrum Master to facilitate Sprint ceremonies (planning, daily scrum, review, retrospective, backlog refinement), manage Scrum artifacts (product backlog, sprint backlog, user stories, tasks), orchestrate developer sub-agents (frontend, backend, full-stack), and track sprint progress. Triggers include sprint planning, daily standup, backlog grooming, sprint review, retrospective, user story creation, task assignment, and sprint initialization.
This skill should be used when the user asks to "implement", "build", "create", "add feature", "develop", "design", "architect", "plan", "structure", "refactor", "improve", "optimize", "review", "fix", "solve", "handle", "debug", or discusses implementation strategies. Apply cognitive load principles to ALL development work as a cornerstone principle.
[DEPRECATED] Persistence logic has been merged into comp-scout-scrape. This skill remains for reference only.
Audit SonarCloud security issues (vulnerabilities and hotspots) for NASA PDS repositories and export to CSV for triage. Use when the user requests SonarCloud security scans, vulnerability reports, or security audits for PDS projects.
Perform organisational mining and handover-of-work analysis with privacy-aware controls.
Chief Architect review - critically evaluate peer feedback on an engineering spec. Integrate valid suggestions, push back on scope creep, and maintain alignment with the PRD. Enforce startup simplicity.
Transform requirements into well-structured User Stories using "As a [user], I want [goal], So that [benefit]" format with Given/When/Then acceptance criteria. Use this skill when: - User asks to "write user story", "create story", "add story" - User mentions "user story", "backlog item", "story" - Running /pm.plan and need to break PRD into implementable stories - Creating backlog items for development team - Need to formalize a requirement into standard story format - Converting feature request into actionable story with acceptance criteria Output: ALWAYS write story files to docs/reference/pm/stories/{story-name}.md
Core development principles for Plan-Marshall projects - when to ask users, research best practices, tool usage, and dependency management
Use when the user wants to log work items (bugs, features, tasks), track time spent, or view a daily/weekly work report.
