Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
77건(striderZA의 저장소) · 인기순
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-time onboarding — asks where you are, then guides you to the right workflow or to pre-workflow exploration. No assumptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure the project's game engine and version. Pins the engine in AGENTS.md, detects knowledge gaps, and populates engine reference docs via webfetch when the version is beyond the LLM's training data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.