deepeshBodh/human-in-loop

記録された最新のソース活動: 2026年3月17日 06:01

SkillsMP カタログ更新: 2026年11月12日 12:52

収集済み skills: 30

GitHub スター: 39
GitHub フォーク: 2

AI アシスタントでインストール

このプロンプトをコピーして、使用中の AI アシスタントに送ってください。

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/deepeshBodh/human-in-loop.

リポジトリの README

README の元ファイル：README.md

README の元ファイルを読む

README 全文を表示

# HumanInLoop **Stop vibe coding. Ship software that lasts.** [Website](https://humaninloop.dev) • [Quick Start](#quick-start) • [Roadmap](./ROADMAP.md) • [Changelog](./CHANGELOG.md) --- ## What is HumanInLoop? HumanInLoop is a Claude Code plugin that enforces **specification-driven development**—ensuring architectural decisions are made by humans before AI writes code. Instead of letting AI improvise your architecture, you guide it through a structured workflow: ``` Idea → Specification → Plan → Tasks → Implementation ``` Every step produces artifacts you can review, refine, and approve before moving forward. --- ## The Workflow ``` ┌──────────────────────────────────────────────────────────────────────────────────┐ │ │ │ ┌─────────┐ ┌─────────┐ ┌──────┐ ┌───────┐ ┌───────────┐ │ │ │ SETUP │─▶│ SPECIFY │─▶│ PLAN │─▶│ TASKS │─▶│ IMPLEMENT │ │ │ └─────────┘ └─────────┘ └──────┘ └───────┘ └───────────┘ │ │ │ │ │ │ │ │ │ ▼ ▼ ▼ ▼ ▼ │ │ ┌─────────┐ ┌─────────┐ ┌──────┐ ┌───────┐ ┌───────────┐ │ │ │ consti- │ │ spec │ │ 6 │ │ tasks │ │ code │ │ │ │ tution │ │ .md │ │ files│ │ .md │ │ changes │ │ │ └─────────┘ └─────────┘ └──────┘ └───────┘ └───────────┘ │ │ │ │ │ │ │ │ │ └────────────┴───────────┴──────────┴────────────┘ │ │ │ │ │ ┌─────▼─────┐ │ │ │ AUDIT │ │ │ │ (review) │ │ │ └───────────┘ │ │ │ │ ○────────○────────○────────○────────○ Human review checkpoints │ │ │ └──────────────────────────────────────────────────────────────────────────────────┘ ``` | Stage | Command | What You Get | |-------|---------|--------------| | **Setup** | `/humaninloop:setup` | Project constitution with your standards | | **Specify** | `/humaninloop:specify` | Structured spec with user stories and requirements | | **Plan** | `/humaninloop:plan` | Technical requirements, constraints, decisions, data models, API contracts | | **Tasks** | `/humaninloop:tasks` | Ordered task list with TDD cycles | | **Audit** | `/humaninloop:audit` | Quality analysis across all artifacts | | **Implement** | `/humaninloop:implement` | Guided implementation with progress tracking | Each command produces artifacts you review before the next step. You stay in control. ### Command Details <details open> <summary>Specify - Create feature specification (DAG-based)</summary> ``` ┌─────────────────────────────────────────────────────────────────────┐ │ /humaninloop:specify │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ │ │ │ SUPERVISOR │ ◄─── You invoke the command │ │ └──────┬───────┘ │ │ │ ┌──────────────────┐ ┌──────────────────┐ │ │ ├─▶│ State Analyst │────▶│ briefing + │ │ │ │ │ (analysis + │ │ assembly + │ │ │ │ │ graph ops) │ │ recommendations │ │ │ │ └──────┬───────────┘ └────────┬─────────┘ │ │ │ │ │ │ │ │ ▼ ▼ │ │ │ ┌──────────────────┐ ┌───────────────────┐ │ │ │ │ Requirements │────▶│ Devil's │ │ │ │ │ Analyst │ │ Advocate │ │ │ │ └────────┬─────────┘ └─────────┬─────────┘ │ │ │ │ │ │ │ │ ▼ ▼ │ │ │ ┌─────────┐ ┌────────────────────┐ │ │ │ │ spec.md │ │ gaps? → new pass │ │ │ │ └─────────┘ └────────────────────┘ │ │ │ │ │ ▼ Deterministic DAG tracks all nodes, edges, and status │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ StrategyGraph JSON (single DAG, multi-pass iteration) │ │ │ └──────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────┘ ``` **Output**: `specs/{feature}/spec.md` + StrategyGraph JSON **Agents**: - **State Analyst** — Strategic analysis + graph mechanics; produces briefings, assembles nodes, freezes passes, and constructs domain agent prompts - **Requirements Analyst** — Transforms feature requests into structured specs; no implementation details - **Devil's Advocate** — Reviews for gaps and ambiguity; asks clarifying questions </details> <details> <summary>Plan - Unified analysis and design planning</summary> ``` ┌─────────────────────────────────────────────────────────────────────┐ │ /humaninloop:plan │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ │ │ │ SUPERVISOR │ ◄─── Reads spec.md │ │ └──────┬───────┘ │ │ │ │ │ ▼ Phase P1 (Analysis) │ │ ┌──────────────────┐ ┌───────────────────┐ ┌─────────────────┐ │ │ │ Technical │─▶│ Principal │─▶│ Devil's │ │ │ │ Analyst │ │ Architect │ │ Advocate │ │ │ └────────┬─────────┘ └───────────────────┘ └────────┬────────┘ │ │ │ (feasibility gate) │ │ │ ▼ ▼ │ │ ┌──────────────┐ ┌───────────────────┐ ┌─────────┐ ┌────────┐ │ │ │requirements │ │constraints-and- │ │ nfrs.md │ │ gaps? │ │ │ │ .md │ │ decisions.md │ │ │ └────────┘ │ │ └──────────────┘ └───────────────────┘ └─────────┘ │ │ │ │ │ Phase P2 (Design) │ │ ▼ │ │ ┌──────────────────┐ ┌─────────────────┐ │ │ │ Technical │────▶│ Devil's │ │ │ │ Analyst │ │ Advocate │ │ │ └────────┬─────────┘ └────────┬────────┘ │ │ │ │ │ │ ▼ ▼ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ data- │ │contracts/│ │quickstart│ │ gaps? │ │ │ │ model.md │ │ api.yaml │ │ .md │ └──────────┘ │ │ └──────────┘ └──────────┘ └──────────┘ │ │ │ │ │ │ │ └──────────┴───────────┘ │ │ │ │ │ ▼ │ │ ┌──────────┐ │ │ │ plan.md │ │ │ └──────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────┘ ``` **Output**: `specs/{feature}/plan.md` + 6 supporting artifacts **Agents**: - **Technical Analyst** — Produces analysis artifacts (requirements, constraints-and-decisions, NFRs) and design artifacts (data model, API contracts, integration guide) - **Principal Architect** — Reviews cross-artifact feasibility after analysis phase (one-time gate) - **Devil's Advocate** — Validates completeness, traceability, and cross-artifact consistency </details> <details> <summary>Tasks - Generate implementation tasks</summary> ``` ┌─────────────────────────────────────────────────────────────────────┐ │ /humaninloop:tasks │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ │ │ │ SUPERVISOR │ ◄─── Reads plan artifacts │ │ └──────┬───────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────┐ ┌───────────────────┐ │ │ │ Task │────▶│ Devil's │ │ │ │ Architect │ │ Advocate │ │ │ └────────┬─────────┘ └─────────┬─────────┘ │ │ │ │ │ │ ▼ ▼ │ │ ┌────────────────┐ ┌──────────┐ │ │ │ task-mapping.md│ │ gaps? │──── yes ──┐ │ │ └────────────────┘ └──────────┘ │ │ │ │ │ ▼ │ │ ▼ no ┌────────────┐ │ │ ┌──────────┐ │ │ clarify w/ │ │ │ │ tasks.md │ ▼ │ user │ │ │ └──────────┘ ┌──────────┐ └─────┬──────┘ │ │ │ done │ │ │ │ └──────────┘ ◄─────┘ (loop) │ │ │ └─────────────────────────────────────────────────────────────────────┘ ``` **Output**: `specs/{feature}/tasks.md` with TDD cycles **Agents**: - **Task Architect** — Maps requirements to vertical slices with TDD structure; no implementation - **Devil's Advocate** — Ensures coverage, proper ordering, and testable increments </details> <details> <summary>Setup - Create project constitution</summary> ``` ┌─────────────────────────────────────────────────────────────────────┐ │ /humaninloop:setup │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ │ │ │ SUPERVISOR │ │ │ └──────┬───────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────┐ Brownfield? │ │ │ Detect Codebase │────────┬──────────────┐ │ │ └──────────────────┘ │ │ │ │ yes no │ │ │ │ │ │ ▼ │ │ │ ┌──────────────────┐ │ │ │ │ Principal │ │ │ │ │ Architect │ │ │ │ └────────┬─────────┘ │ │ │ │ │ │ │ ┌───────────────────┼───────────────┤ │ │ ▼ ▼ ▼ │ │ ┌────────────┐ ┌────────────────┐ ┌────────────┐ │ │ │ codebase- │ │ constitution │ │constitution│ │ │ │analysis.md │ │ .md │ │ .md │ │ │ └────────────┘ └────────────────┘ └────────────┘ │ │ │ │ │ │ ▼ │ │ │ ┌────────────┐ │ │ │ │ evolution- │ │ │ │ │ roadmap.md │ │ │ │ └────────────┘ │ │ │ └───────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────┘ ``` **Output**: `.humaninloop/memory/constitution.md` **Agents**: - **Principal Architect** — Defines governance principles and quality gates; enforces RFC 2119 keywords </details> <details> <summary>Audit - Analyze artifacts for quality</summary> ``` ┌─────────────────────────────────────────────────────────────────────┐ │ /humaninloop:audit │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ │ │ │ SUPERVISOR │ ◄─── No agents, direct analysis │ │ └──────┬───────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ Load Artifacts │ │ │ │ spec.md │ plan.md │ tasks.md │ data-model │ contracts │ │ │ └──────────────────────────┬───────────────────────────────┘ │ │ │ │ │ ┌───────────────────┼───────────────────┐ │ │ ▼ ▼ ▼ │ │ ┌────────────┐ ┌────────────┐ ┌────────────┐ │ │ │ Spec │ │ Plan │ │ Task │ │ │ │ Analysis │ │ Validation│ │ Validation │ │ │ └────────────┘ └────────────┘ └────────────┘ │ │ │ │ │ │ │ └───────────────────┴───────────────────┘ │ │ │ │ │ ▼ │ │ ┌────────────────┐ │ │ │ Audit Report │ │ │ │ (stdout/file) │ │ │ └────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────┘ ``` **Output**: Coverage report + flagged issues **Agents**: None — direct analysis using validation skills </details> <details> <summary>Implement - Execute the task plan</summary> ``` ┌─────────────────────────────────────────────────────────────────────┐ │ /humaninloop:implement │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ │ │ │ SUPERVISOR │ ◄─── Reads tasks.md │ │ └──────┬───────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ Foundation Cycles (Sequential) │ │ │ │ C1 ──▶ C2 ──▶ C3 ──▶ ... │ │ │ └──────────────────────────┬───────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ Feature Cycles (Can Parallel) │ │ │ │ C4 ──┬──▶ C5 │ │ │ │ └──▶ C6 [P] │ │ │ └──────────────────────────┬───────────────────────────────┘ │ │ │ │ │ For each cycle: │ │ │ ┌──────────────────────────┴───────────────────────────────┐ │ │ │ T1 (test) ──▶ T2 (impl) ──▶ T3 (impl) ──▶ Checkpoint │ │ │ │ │ │ │ │ │ ▼ (if TEST: marker) │ │ │ │ ┌─────────────────┐ │ │ │ │ │ QA Engineer │ ──▶ auto-approve or human checkpoint│ │ │ │ └─────────────────┘ │ │ │ └──────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────┘ ``` **Output**: Implemented code + marked tasks **Agents**: - **QA Engineer** — Executes verification tasks and captures evidence; auto-approves or presents checkpoints </details> --- ## What's Included ### 6 Commands The full specify → plan → tasks → implement lifecycle. ### 29 Skills Claude automatically invokes these when relevant—authoring requirements, technical specifications, analyzing codebases, designing APIs, running verification tests, managing GitHub issues, workflow strategy, and more. ### 9 Specialized Agents Focused responsibilities: requirements analyst, technical analyst, devil's advocate, principal architect, task architect, staff engineer, QA engineer, UI designer, state analyst. See the [plugin documentation](./plugins/humaninloop/README.md) for full details. --- ## Quick Start ### 1. Add the marketplace ```bash /plugin marketplace add deepeshBodh/human-in-loop ``` ### 2. Install the plugin ```bash /plugin install humaninloop ``` ### 3. Install and configure the `hil-dag` MCP server (required for specify and implement) ```bash uv tool install "humaninloop-brain @ git+https://github.com/deepeshBodh/human-in-loop.git#subdirectory=humaninloop_brain" ``` Then configure the MCP server in your Claude Code settings (`.claude/settings.json`): ```json { "mcpServers": { "hil-dag": { "command": "hil-dag" } } } ``` **To upgrade to the latest version:** ```bash uv tool install --force "humaninloop-brain @ git+https://github.com/deepeshBodh/human-in-loop.git#subdirectory=humaninloop_brain" ``` ### 4. Set up your project ```bash /humaninloop:setup ``` This creates your project constitution—the standards and conventions that guide all future specifications. ### 5. Create your first spec ```bash /humaninloop:specify add user authentication with email and password ``` --- ## Documentation | Resource | Description | |----------|-------------| | [Roadmap](./ROADMAP.md) | Vision and planned features | | [Changelog](./CHANGELOG.md) | Release history | | [Plugin README](./plugins/humaninloop/README.md) | Detailed command and skill reference | --- ## For Plugin Developers This repository serves as a reference implementation for Claude Code plugins. If you're building your own plugins, you can learn from: ### Repository Structure ``` human-in-loop/ ├── humaninloop_brain/ # Deterministic DAG infrastructure (Python) │ ├── src/humaninloop_brain/ # Package source │ │ ├── entities/ # Pydantic models (11 enums, 14 models) │ │ ├── graph/ # NetworkX graph operations │ │ ├── validators/ # Structural + contract validators │ │ ├── passes/ # Pass lifecycle management │ │ ├── mcp/ # MCP server + transport-agnostic operations │ │ └── cli/ # CLI adapter (delegates to mcp/operations) │ └── tests/ # 403 tests, ~95% coverage ├── plugins/humaninloop/ │ ├── .claude-plugin/plugin.json # Plugin manifest │ ├── commands/ # Slash command definitions │ ├── agents/ # 9 specialized agent definitions │ ├── skills/ # 29 model-invoked skills │ ├── catalogs/ # Node catalogs for DAG workflows │ ├── templates/ # Workflow templates │ └── scripts/ # Shell utilities ├── docs/ │ ├── decisions/ # Architecture Decision Records (8 ADRs) │ ├── architecture/ # DAG-first + v3 architecture docs │ ├── claude-plugin-documentation.md │ └── agent-skills-documentation.md └── specs/ # Feature specifications (dogfooding) ``` ### Key Resources - [Claude Code Plugin Documentation](./docs/claude-plugin-documentation.md) - Complete technical reference - [Agent Skills Documentation](./docs/agent-skills-documentation.md) - How skills work - [Architecture Decisions](./docs/decisions/) - ADRs explaining design choices --- ## Contributing See [CONTRIBUTING.md](./CONTRIBUTING.md) for guidelines. --- ## License MIT - See [LICENSE](./LICENSE)

リポジトリの README を読み込んでいます…

このリポジトリの skills

ソフトウェア開発者ソフトウェア品質保証アナリスト・テスターコンピュータシステムアナリストグラフィックデザイナー

13 件の職業カテゴリ · 100% 分類済み

skill

職業分類

説明

更新

strategy-implementation

プロジェクト管理専門家

This skill MUST be invoked when the user says "implementation strategy", "cycle sequencing", or "implement workflow patterns". SHOULD also invoke when user mentions "execute-then-verify", "targeted retry", "fix pass", or "implementation escalation". Provides…

原文の言語: 英語

2026-03-17

auditing-agents

その他コンピュータ職

This skill MUST be invoked when the user says "audit agent", "review agent", "check agent compliance", or "agent audit checklist". SHOULD also invoke when user mentions "AGENT-GUIDELINES compliance", "agent review", or "coupling detection". Provides the…

原文の言語: 英語

2026-03-17

executing-tdd-cycle

ソフトウェア品質保証アナリスト・テスター

This skill MUST be invoked when the user says "execute cycle", "implement tasks", "TDD cycle", or "red green refactor". SHOULD also invoke when implementing cycle task lists, encountering `[EXTEND]`/`[MODIFY]` markers, generating cycle reports, or handling…

原文の言語: 英語

2026-03-17

patterns-vertical-tdd

ソフトウェア開発者

This skill MUST be invoked when the user says "create task mapping", "structure implementation", "define cycles", "vertical slice", "TDD", "test first", "cycle structure", or "testable increment". SHOULD also invoke when user mentions "red green refactor" or…

原文の言語: 英語

2026-03-17

testing-end-user

ソフトウェア品質保証アナリスト・テスター

This skill MUST be invoked when the user says "TEST:", "TEST:VERIFY", "TEST:CONTRACT", "execute verification", "run test task", or "verification test". SHOULD also invoke when the user says "Setup/Action/Assert", "verify against infrastructure", or "capture…

原文の言語: 英語

2026-03-17

authoring-technical-requirements

コンピュータ・情報システムマネージャー

This skill MUST be invoked when the user says "write technical requirements", "define constraints", "define NFRs", "map integrations", "classify data sensitivity", or "infrastructure requirements". SHOULD also invoke when user mentions "TR-", "C-", "NFR-",…

原文の言語: 英語

2026-03-16

brownfield-integration

ソフトウェア開発者

This skill MUST be invoked when the user says "brownfield integration", "extend existing code", or "modify existing file". SHOULD also invoke when encountering tasks with `[EXTEND]` or `[MODIFY]` markers, implementing against existing codebases, or…

原文の言語: 英語

2026-03-16

validation-plan-artifacts

ソフトウェア品質保証アナリスト・テスター

This skill MUST be invoked when the user says "review research", "review data model", "review contracts", "plan quality", "phase review", or "design gaps". SHOULD also invoke when user mentions "artifact review" or "planning validation".

原文の言語: 英語

2026-03-16

validation-task-artifacts

ソフトウェア品質保証アナリスト・テスター

This skill MUST be invoked when the user says "review task mapping", "review tasks", "validate cycles", or "check TDD structure". SHOULD also invoke when user mentions "task quality", "cycle review", "vertical slice", or "task artifact".

原文の言語: 英語

2026-03-16

patterns-technical-decisions

プロジェクト管理専門家その他コンピュータ職

This skill MUST be invoked when the user says "evaluate alternatives", "make technology choice", "document decision", "technology choice", "trade-offs", "decision record", "rationale", or "why we chose". SHOULD also invoke when user mentions "alternatives" or…

原文の言語: 英語

2026-03-16

strategy-core

管理サービスマネージャー

Universal workflow patterns (validation, gap classification, pass evolution, halt escalation) consumed by the State Analyst to inform Supervisor briefings.

原文の言語: 英語

2026-02-18

strategy-specification

マーケティングマネージャー

Specification-workflow patterns (input assessment, produce-then-validate, gap-informed revision) consumed by the State Analyst alongside strategy-core for targeted Supervisor briefings.

原文の言語: 英語

2026-02-18

analysis-screenshot

グラフィックデザイナー

This skill MUST be invoked when the user says "analyze screenshot", "extract design tokens", "pull colors from screenshot", "component inventory", "break down this UI", or "design extraction". SHOULD also invoke when user mentions "screenshot", "color…

原文の言語: 英語

2026-02-07

authoring-design-system

グラフィックデザイナー

This skill MUST be invoked when the user says "assemble design system", "build design system", "merge extractions", "consolidate tokens", "unify design tokens", or "synthesize design system". SHOULD also invoke when user mentions "design system", "token…

原文の言語: 英語

2026-02-07

patterns-flow-mapping

ウェブ・デジタルインターフェースデザイナーソフトウェア開発者

This skill MUST be invoked when the user says "map the flow", "connect these screens", "build user journey", "navigation mapping", "interaction flow", or "flow diagram". SHOULD also invoke when user mentions "screen transitions", "user flow", "navigation…

原文の言語: 英語

2026-02-07

analysis-iterative

ソフトウェア開発者

This skill MUST be invoked when the user says "brainstorm", "deep analysis", "let's think through", "analyze this with me", or "help me think through". SHOULD also invoke when feature descriptions lack Who/Problem/Value clarity during specification enrichment.

原文の言語: 英語

2026-02-06

patterns-interface-design

グラフィックデザイナー

This skill MUST be invoked when the user says "interface design", "UI design", "component design", "visual design", "styling", "dark mode", "spacing", "typography hierarchy", or "surface elevation". SHOULD also invoke when user mentions "frontend aesthetics"…

原文の言語: 英語

2026-02-05

using-git-worktrees

ソフトウェア開発者

This skill MUST be invoked when the user says "create worktree", "isolated workspace", "parallel branch work", "git worktree", "feature isolation", or "branch workspace". SHOULD also invoke when starting feature work that needs isolation from current…

原文の言語: 英語

2026-02-05

analysis-codebase

コンピュータシステムアナリスト

This skill MUST be invoked when the user says "analyze codebase", "scan project", "detect tech stack", "codebase analysis", "collision risk", or "brownfield". SHOULD also invoke when user mentions "existing code" or "project context".

原文の言語: 英語

2026-02-05

authoring-constitution

広告・プロモーションマネージャー

This skill MUST be invoked when the user says "write principles", "define governance", "create constitution", or "write a constitution". SHOULD also invoke when user mentions "governance", "principles", "enforcement", or "amendment process". Core skill for…

原文の言語: 英語

2026-02-05

authoring-roadmap

ソフトウェア開発者

This skill MUST be invoked when the user says "roadmap", "gap analysis", "evolution plan", "brownfield gaps", or "improvement priorities". Use for creating evolution roadmaps and identifying improvement priorities for brownfield projects.

原文の言語: 英語

2026-02-05

brownfield-constitution

ソフトウェア開発者

This skill MUST be invoked when the user says "create constitution for existing codebase", "codify existing patterns", "brownfield constitution", "essential floor", or "emergent ceiling". SHOULD also invoke when user mentions "brownfield", "evolution…

原文の言語: 英語

2026-02-05

syncing-claude-md

ソフトウェア開発者

This skill MUST be invoked when the user says "sync CLAUDE.md", "update agent instructions", "propagate constitution changes", "CLAUDE.md sync", or "constitution alignment". SHOULD also invoke when user mentions "agent instructions" updates.

原文の言語: 英語

2026-02-05

validation-constitution

ソフトウェア品質保証アナリスト・テスター

This skill MUST be invoked when the user says "review constitution", "validate principles", "check quality", "constitution review", "quality check", "version bump", "anti-patterns", or "constitution audit".

原文の言語: 英語

2026-02-05

analysis-specifications

コンピュータシステムアナリスト

This skill MUST be invoked when the user says "review spec", "find gaps", "what's missing", or "clarify requirements". SHOULD also invoke when reviewing spec.md for completeness. Focuses on product decisions and generates clarifying questions with concrete…

原文の言語: 英語

2026-02-05

patterns-api-contracts

コンピュータシステムアナリスト

This skill MUST be invoked when the user says "design API", "map endpoints", "define schemas", "API contract", "REST API design", or "OpenAPI spec". SHOULD also invoke when user mentions "endpoint", "schema", "contract", or "HTTP".

原文の言語: 英語

2026-02-05

patterns-entity-modeling

データベースアーキテクト

This skill MUST be invoked when the user says "extract entities", "define data model", "model relationships", "entity modeling", or "domain model". SHOULD also invoke when user mentions "relationship", "cardinality", "state machine", or "data attributes".

原文の言語: 英語

2026-02-05

authoring-user-stories

コンピュータシステムアナリスト

This skill MUST be invoked when the user says "write user stories", "define acceptance criteria", "prioritize features", "user story", "acceptance scenario", or "Given When Then". SHOULD also invoke when user mentions "priority", "P1", "P2", "P3", or…

原文の言語: 英語

2026-02-05

authoring-requirements

ソフトウェア開発者

This skill MUST be invoked when the user says "write requirements", "define success criteria", "identify edge cases", or "functional requirements". SHOULD also invoke when user mentions "FR-", "SC-", "RFC 2119", "MUST SHOULD MAY", or "edge cases". Produces…

原文の言語: 英語

2026-02-05

using-github-issues

コンピュータユーザーサポートスペシャリスト

This skill MUST be invoked when the user says "report a bug", "create issue", "log issue", "file a bug", "raise an issue", "create bug", or "feature request". Use for GitHub issue creation, lifecycle management, triage, and structured issue tracking.

原文の言語: 英語

2026-01-25

収集済み skill 30 件中 30 件を表示しています。