mism-dev-story-lean

Implements one lean mismAgent task in red-green-refactor until tests and contract tests pass.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lucolucus/mismagent --skill mism-dev-story-lean-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mism-dev-story-lean
Source: https://github.com/lucolucus/mismagent/tree/main/attic/skills/mism-dev-story-lean
Command: npx skills add https://github.com/lucolucus/mismagent --skill mism-dev-story-lean-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It implements a single mismAgent lean task (Gherkin acceptance criteria plus contract reference) without polluting the task file with state sections, since in mismAgent the folder location itself is the state and only the orchestrator moves tasks. ## Core Features & Use Cases - Red-Green-Refactor per AC: Writes a failing test first, then the minimal implementation, then refactors, covering every Gherkin acceptance criterion. - Contract-driven development: Resolves the contract via contract_ref.operationId, uses contract-generated types, and runs the side's gate commands (build, test, contract-test) until green. - Strict structured return: Emits a machine-readable RESULT (READY-FOR-REVIEW, BLOCKED, or BOUNCED) with branch, files changed, and test status, never touching Status, File List, Change Log, or dag.yaml. - Use Case: An orchestrator dispatches a backend task file to this skill with a working directory and story branch; the skill implements the endpoint, adds a response-shape contract test, commits per functionality, and returns READY-FOR-REVIEW. ## Quick Start Implement the mismAgent task at the given absolute path in the specified working directory on the given story branch, following red-green-refactor until all gate commands pass.

Frequently Asked Questions about mism-dev-story-lean

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a mismAgent lean task with this skill?

Provide the absolute path of the lean task file, the working directory, and the story branch name. The skill resolves the contract via contract_ref.operationId, runs red-green-refactor for each Gherkin acceptance criterion, and returns a strict RESULT block when all gate commands pass.

Why does this skill forbid writing Status or Change Log sections into the task file?

In mismAgent the state is the folder location (backlog, todo, doing, done), and only the orchestrator moves tasks via git mv. Writing state sections or a status field into the file is a forbidden invariant; the permanent journal is the git log.

What happens when a task has ambiguous acceptance criteria or an unresolvable contract?

The skill does not invent missing details. It returns BOUNCED with a description of what is missing, signaling the task is under-refined so the orchestrator sends it back to the backlog.

Can this skill commit code across multiple repos or sides?

No. It works only in the indicated working directory using git -C, and never codes for one side in another side's repo. If crossing the boundary would be required, it returns BLOCKED instead.

What does the skill return when implementation is complete?

It returns a strict block with RESULT set to READY-FOR-REVIEW, plus TASK_ID, BRANCH, SUMMARY, FILES_CHANGED, FILE_LIST, TESTS_ADDED, and TESTS_PASSING. READY-FOR-REVIEW requires green build, test, and contract-test gates with every acceptance criterion covered.