humaninloop

Plugin humaninloop from marketplace humaninloop-plugins in deepeshBodh/human-in-loop. Commands read from the repo's manifest — 1 month ago.

Skills (29)

• 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".

• 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.

• 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 palette", "typography", "spacing", or "component

• 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 options.

• 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 greenfield projects.

• 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 consolidation", "component normalization", or

• 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 technology-agnostic requirements in FR-XXX

• 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.

• 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-", "IP-", "INT-", "DS-", "non-functional", "sy

• 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 "backlog". Produces prioritized user stories with

• 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 roadmap", or "legacy project". Extends authoring-

• 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 integrating with established interfaces.

• 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 retry after checkpoint failure.

• 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".

• 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".

• 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 architecture", "entry points", "dead ends", o

• 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" or "UI components".

• 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 "NEEDS CLARIFICATION".

• 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 "implementation tasks".

• strategy-core

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

• 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 implementation-workflow patterns consumed

• 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.

• 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.

• 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 evidence".

• 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 workspace.

• 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.

• 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".

• 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".

• 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".

Slash commands (7)

• /humaninloop:audit

  Comprehensive artifact analysis with reviewer-friendly output mode. Consolidates checklist and analyze functionality.

• /humaninloop:implement

  Execute the implementation plan using DAG-based workflow execution

• /humaninloop:plan

  Execute the multi-agent implementation planning workflow with specialized agents and validation loops

• /humaninloop:setup

  Create or update the project constitution using the Principal Architect agent.

• /humaninloop:specify

  Create feature specification using DAG-based workflow execution

• /humaninloop:tasks

  Execute the multi-agent task generation workflow with specialized agents and validation loops

• /humaninloop:techspec

  [DEPRECATED] Use /humaninloop:plan instead. The techspec workflow has been merged into the unified plan command.

Subagents (9)

• devils-advocate

  Adversarial reviewer who stress-tests specifications, planning artifacts, and task artifacts by finding gaps, challenging assumptions, and identifying edge cases. Asks the hard "what if" questions that prevent costly surprises during implementation. <example> Context: User has a feature spec they wa

• principal-architect

  Senior technical leader who brings governance judgment. Evaluates whether standards are enforceable, testable, and justified. Rejects vague aspirations in favor of actionable constraints. <example> Context: User is starting a new project and needs governance principles established user: "We need a c

• qa-engineer

  Senior QA engineer who treats verification as an engineering discipline. Executes structured verification tasks, captures evidence, and gates cycle completion on human approval. <example> Context: Implementation is complete and needs verification before approval user: "Implementation is done. Run th

• requirements-analyst

  Senior analyst who transforms vague feature requests into precise, implementable specifications. Excels at eliciting requirements through structured discovery, identifying assumptions, and producing clear user stories with measurable acceptance criteria.

• staff-engineer

  Staff Software Engineer who implements code via TDD discipline. Executes cycle task lists with red/green/refactor rigor, handles brownfield integration, and produces honest cycle reports. <example> Context: Supervisor dispatches Staff Engineer for a normal cycle execution user: "Read your instructio

• state-analyst

  Produces decision-ready briefings, manages DAG graph mechanics, and advances workflow state. Combines strategic analysis (briefings, report parsing, recommendations) with graph operations (node assembly, pass freezing, status updates). The Supervisor delegates all DAG operations and state analysis t

• task-architect

  Senior architect who transforms planning artifacts into implementation tasks through vertical slicing and TDD discipline. Produces task mappings and cycle-based task lists that enable incremental, testable delivery.

• technical-analyst

  Senior systems engineer who bridges the gap between business specifications and technical implementation through requirements analysis AND concrete design decisions. Decomposes business intent into precise, traceable technical requirements, then transforms those requirements into entity models, API

• ui-designer

  Senior interface designer who analyzes visual inspiration from existing apps to extract design patterns, build actionable design systems, and craft screen layouts and interaction flows for projects. <example> Context: User has screenshots from apps they admire and wants to build a design system user

Similar plugins