fc-workflow
FC 온보딩 워크플로우 이해 및 상태 관리 가이드. FC 상태, 위촉 프로세스, 권한 관련 질문 시 사용.
FC 온보딩 워크플로우 이해 및 상태 관리 가이드. FC 상태, 위촉 프로세스, 권한 관련 질문 시 사용.
BacklogのIdeaを、実装着手可能なSpec(Ready)として specs/NNN_feature/spec.md に昇格し、specs/INDEX.md を更新する。実装は行わず、ドキュメント作成と索引更新のみを行う。Use when the user wants to promote a backlog idea to Ready status for implementation.
Manage complex task dependencies with beads, resolve blockers, and optimize task execution order
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
Convert Spec Kit task list markdown files to bd (Beads) issues with proper hierarchy
Manages task complexity scoring and dynamic iteration limits. Decomposes problems into atomic items, scores complexity, and allocates appropriate loop counts. Use when tackling multi-step problems that need structured iteration management.
Checks essential information and project status before starting a task.
ATS scoring integration, analysis, optimization suggestions, format compatibility checks, and score tracking. Use when asked to improve ATS scores, interpret Jobscan results, or generate ATS-safe recommendations.
Generate high-level tasks and gated sub-tasks from a PRD, with agent assignments, commit/PR strategy, and relevant files.
Generate high-level tasks and gated sub-tasks from a PRD, with agent assignments, commit/PR strategy, and relevant files.
Software engineering base skills for Giant Swarm staff
Triage extension for marketplace plugin findings during plan-finalize phase
Comprehensive guide to Agile Scrum methodology including roles, ceremonies, artifacts, sprint planning, and best practices for iterative software development
Scrum Master & Engineering-Oriented Delivery Lead with hands-on frontend/backend development experience. Interprets Technical Design Documents, reviews UX/UI designs, and understands product requirements to ensure delivery clarity. Breaks features into well-scoped Scrum stories (max 3 story points, Fibonacci estimation). Stories are sliced for incremental value, minimal risk, fast feedback. For every ticket provides: clear description, explicit acceptance criteria, expected behavior, constraints, and test case expectations (happy path + edge cases). Ensures stories are implementation-ready, testable, aligned with technical/product goals. Enables team to execute efficiently while maintaining high quality and predictable velocity. Use when creating sprint stories, planning sprints, estimating work, or breaking down features into tickets.
Workflow bug triage for OpenEvent. Use when you have a regression/bug report (wrong step, wrong detour, HIL stuck, site visit issues) and need a minimal reproduction trace plus a fix plan tied to workflow invariants and tests.
recenter on where we are, what's done/left, and where necessary reflect on our work's principle compliance, performance, and pristineness.
Use when implementing features, writing code, executing implementation plans, practicing TDD, or making code changes based on a plan.
Do research step of the PREP phase of star-team workflow.