Run any Skill in Manus with one click

Get Started

hima-trial

Stars1

Forks0

UpdatedJuly 2, 2026 at 18:59

Write and run the tests that prove each charter scenario; accumulate the evidence no completion claim may skip.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

momomuchu

momomuchu/hima

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	hima-trial
description	Write and run the tests that prove each charter scenario; accumulate the evidence no completion claim may skip.
stage	test
source	base
mode	force

Purpose

Cover the cycle's test stage: prove every charter scenario with real tests (unit, integration, e2e as appropriate) and accumulate the evidence set that hima-verdict will check. Force at M+ criticality — no DONE claim is trusted without trial evidence behind it.

When to use

A sealed charter exists and its scenarios need a corresponding test before (RED) or after (confirming GREEN) hima-forge writes code.
A completion claim is about to be made and no test evidence has been collected yet for one or more charter scenarios.

Steps

For every Gherkin scenario in the charter, write (or confirm) a corresponding test — no scenario without a test.
Write tests RED first when practical; otherwise confirm they fail for the right reason before hima-forge makes them pass.
Prefer integration-level tests for behavior, unit tests for pure domain logic — never test mocks in place of real behavior.
Run the full relevant suite, not just the new tests, to catch regressions.
Record the evidence set (which scenario → which test → pass/fail) so hima-verdict can audit it without re-deriving it.

Done when

Every charter scenario has a passing test that exercises real behavior, not a mock of itself.
The full relevant test suite is green, not just the newly added tests.
The evidence set is written down and ready for hima-verdict's independent check.

More from this repository

same repository

hima-admit

momomuchu/hima

Bootstrap a new project or catch up an agent on an existing one in minutes by reading vision/goals/state and scaffolding the minimum brain files.

2026-07-021

hima-blueprint

momomuchu/hima

Produce the structural plan — component boundaries, contracts, data flow — plus a lightweight decision record, from a sealed charter.

2026-07-021

hima-charter

momomuchu/hima

Formalize intent into a spec artifact (Gherkin scenarios, acceptance criteria, criticality tags) before any non-md file may change.

2026-07-021

hima-covenant

momomuchu/hima

Declare and audit the per-project disciplines (cadence, branching, testing, architecture, methodology) that the pluggable StageSkillMap resolves against.

2026-07-021

hima-forge

momomuchu/hima

Implement the minimum code to satisfy the charter's RED tests, one logical change per commit.

2026-07-021

hima-lookout

momomuchu/hima

Cited, multi-source research pass for H/C decisions or true blockers — converts findings into requirements, risks, and rejected alternatives.

2026-07-021

name	hima-trial
description	Write and run the tests that prove each charter scenario; accumulate the evidence no completion claim may skip.
stage	test
source	base
mode	force

Purpose

When to use

A sealed charter exists and its scenarios need a corresponding test before (RED) or after (confirming GREEN) hima-forge writes code.
A completion claim is about to be made and no test evidence has been collected yet for one or more charter scenarios.

Steps

For every Gherkin scenario in the charter, write (or confirm) a corresponding test — no scenario without a test.
Write tests RED first when practical; otherwise confirm they fail for the right reason before hima-forge makes them pass.
Prefer integration-level tests for behavior, unit tests for pure domain logic — never test mocks in place of real behavior.
Run the full relevant suite, not just the new tests, to catch regressions.
Record the evidence set (which scenario → which test → pass/fail) so hima-verdict can audit it without re-deriving it.

Done when

Every charter scenario has a passing test that exercises real behavior, not a mock of itself.
The full relevant test suite is green, not just the newly added tests.
The evidence set is written down and ready for hima-verdict's independent check.