Menu
SkillsMP has collected 18 skills from River-181/harness-engineering-skills. Open a skill to review its source and details.
Showing 18 of 18 collected skills.
Use when designing AI Agent product capabilities, competition judging evidence, or production agent safety. Creates judgment → action → verification/improvement loops with retrieval, rule checks, approval, logging, and feedback.
Use after PRD/domain model and before implementation. Designs system architecture, component boundaries, dataflow, integration points, security boundaries, logging, audit, failure handling, and demo-vs-production separation.
Use before asking coding agents to implement features, especially when outputs must converge across Claude, Codex, Gemini, or human maintainers. Creates deterministic code-generation rules for naming, imports, exports, folders, APIs, UI states, tests, lint…
Use when the team needs a clear why, strategic narrative, problem definition, or scope boundary before PRD or implementation. Frames a product or feature using Context → Problem → Solution.
Use before CPS, PRD, pitch, or competition submission when a product needs a sharp data-driven business model. Creates the 11-block DDBM canvas, data asset assumptions, risk linkage, cost/revenue model, and judge-facing business thesis.
Use before presentation, judging, client delivery, sprint closeout, or team handoff. Prepares final demo script, runbook, handoff document, known limitations, change history, maintainer notes, and submission-readiness package.
Use before architecture, database design, code generation, or AI Agent implementation. Builds an implementation-ready domain model with entities, relationships, states, transitions, events, permissions, and audit relationships.
Use when a project needs proof that agent outputs remain useful, grounded, safe, and maintainable over time. Creates organization-specific evals: golden cases, rubrics, failure modes, regression schedule, cross-agent normal-form comparison, and safety gates.
Use at the start of a product, AI Agent, MVP, or enterprise delivery repo, or when a repo lacks harness.yaml, docs, rules, evals, and CLAUDE.md project memory. Creates a complete local harness scaffold.
Use before CPS, PRD, or implementation when raw transcripts, notes, client conversations, brainstorms, or vague requirements need normalization. Converts them into source logs, meeting logs, explicit/implied requirements, decisions, open questions, and build…
Use for JB금융그룹 Fin:AI 본선/예선 work or similar financial AI Agent competitions. Aligns a financial AI Agent MVP, proposal, feature specification, demo flow, change log, and risk controls to judging criteria.
Use when moving from framing to buildable scope. Creates PRD, MVP proposal, and implementation-ready feature specs traced to CPS, users, scenarios, acceptance criteria, demoability, and risk controls.
Use when terms drift, the team needs non-negotiables, or downstream docs/code need consistent names. Defines enforceable project principles, canonical vocabulary, anti-synonyms, and concept hierarchy.
Use for regulated, financial, customer-facing, enterprise, or high-risk workflows that need reviewable engineering controls. Creates operational risk, privacy, security, compliance, approval, audit, copyright, hallucination, explainability, and responsibility…
Use when the user asks what to do next, gives messy product/enterprise AI/FDE/MVP/agent-delivery requirements, asks for a harness, or requests implementation before discovery artifacts exist. Routes the request into the right Harness Engineering lifecycle…
Use when maintaining or releasing the Harness Engineering Skill Pack itself. Adds skills, tunes trigger descriptions, shrinks or expands playbooks, adds templates/evals, updates scripts, runs audits, and prepares release notes.
Use when a vague product may require multiple apps, consoles, portals, dashboards, APIs, actors, permissions, or action boundaries. Decomposes a product into user-facing and operator-facing software surfaces by actor, job, permission, data access, action…
Use before implementation, submission, demo, handoff, or public release. Validates the current project harness for required files, sections, placeholders, traceability, gates, risk disclosures, and readiness.