「develop」の検索結果

PM (Project Manager / Scrum Master) agent. Reads BA and TechLead artifacts and produces sprint plan, task breakdown, and story point estimates. Creates one TodoWrite entry per sprint task for live pipeline tracking (FR-42). Part of the Virtual Team Skill pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

TechLead (Senior Technical Lead) agent. Reads all BA artifacts and produces system architecture, technology stack, ERD, sequence diagrams, and ADRs. Declares Gate 1: Design Freeze. Part of the Virtual Team Skill pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Full SRS workflow: Brainstorm → Spec → Plan (per-section files) → User Review → SRS Generation → Validation → Improvement Report → Context Save. Use when user provides a project topic and wants a complete requirements pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 7 of the SRS workflow. Runs srs_validator.py --dir on the generated SRS files, reports errors and warnings, auto-fixes ERRORs, and outputs a COMPLIANT / PARTIALLY COMPLIANT / NON-COMPLIANT verdict.

日本語の概要は準備中です。原文の説明を表示しています。

Independent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.

日本語の概要は準備中です。原文の説明を表示しています。

BA (Business Analyst) agent. Analyzes requirements and produces 4 artifact files: requirements.md, user-stories.md, acceptance-criteria.md, business-rules.md. Use --spec <path> to load requirements from any markdown file. Part of the Virtual Team Skill pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 4 of the SRS workflow. Reads spec.md and writes one detailed plan file per SRS section (§1–§3 + Appendices). Each file is a complete blueprint for the corresponding SRS section. No word limit.

日本語の概要は準備中です。原文の説明を表示しています。

Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.

日本語の概要は準備中です。原文の説明を表示しています。

Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.

日本語の概要は準備中です。原文の説明を表示しています。

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.

日本語の概要は準備中です。原文の説明を表示しています。

Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.

日本語の概要は準備中です。原文の説明を表示しています。

Full-pipeline orchestrator. Runs all 7 agents (BA → TechLead → PM → BE Dev → FE Dev → Tester → QA/QC) in sequence by invoking each per-agent skill via the Skill tool. All writes go through the pre_write_validator.py hook for hard enforcement. Use per-agent commands (/team-ba, /team-techlead, etc.) for manual control.

日本語の概要は準備中です。原文の説明を表示しています。

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

日本語の概要は準備中です。原文の説明を表示しています。

Dispatch to the right problem-solving technique based on how you're stuck

日本語の概要は準備中です。原文の説明を表示しています。

Phase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.

日本語の概要は準備中です。原文の説明を表示しています。

Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales

日本語の概要は準備中です。原文の説明を表示しています。

Phase 9 of the SRS workflow. Saves all project context to _context/ files so future sessions can resume without re-reading the full SRS.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 6 of the SRS workflow. Reads approved plan files and generates a complete IEEE 830-compliant SRS — one file per section, no word limit. A full SRS may span 300+ pages across all files.

日本語の概要は準備中です。原文の説明を表示しています。

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

日本語の概要は準備中です。原文の説明を表示しています。

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

日本語の概要は準備中です。原文の説明を表示しています。