mismagent-harvest-dev-architecture

Generates a dev-architecture skill by harvesting conventions from completed code blocks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After the first green wave of a mismAgent build, workers keep reinventing conventions because no architecture memory exists yet. This Skill turns the stabilized conventions of real, merged code into a dev-architecture skill that every future mismagent-worker loads, so patterns stop being rediscovered per dispatch. ## Core Features & Use Cases - Convention harvesting: Reads only the DONE blocks' code and extracts layout, naming, test patterns, per-block-type patterns, and toolchain quirks, each backed by 1-2 golden exemplar files cited by path. - Conflict resolution: When two competing patterns exist in the code, both are presented to the user who picks the canonical one; inconsistencies are never harvested as rules. - Memory generation and reconciliation: Writes a compact <side>-dev-architecture/SKILL.md (Claude Code: .claude/skills/, Codex: .agents/skills/) and points the profile's sides.<side>.dev_architecture at it, reconciling against any architect-authored doc written before the first domain wave. - Use Case: After your first vertical slice passes the gate, run the harvest so the next worker dispatch loads real naming, test-shape, and presenter/persistence conventions instead of inventing them. ## Quick Start Ask the agent to harvest the dev-architecture conventions from the done blocks of the active profile and generate the dev-architecture skill for the codebase.

Frequently Asked Questions about mismagent-harvest-dev-architecture

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

FAQPage Schema
How do I generate a dev-architecture skill from existing code?

Run the harvest after at least one wave or slice is green. It reads only the done blocks' code, extracts conventions per dimension with golden exemplar files, presents the summary for your confirmation, then writes the dev-architecture SKILL.md and updates the profile.

When should I run the architecture harvest in mismAgent?

Run it after the first green wave or slice, once patterns have stabilized, or when workers start reinventing conventions. Running it too early harvests noise, since one block is anecdote while a slice is a pattern.

What is the difference between the descriptive and prescriptive architecture routes?

The prescriptive route is an architect-authored doc written before the first domain wave in greenfield projects. The descriptive route is this harvest, derived only from real code, which later grounds and reconciles that authored doc against what was actually built.

Does the harvest create one architecture memory per deploy role?

No. The memory attaches to the codebase, not the deploy role. Sides sharing one domain codebase get a single shared memory, and the profile's dev_architecture field is set to the same value for every side using that codebase.

What happens when the code contains two competing conventions?

Conflicts are treated as decisions, not averages. Both patterns are brought to the user, who picks the canonical one; the choice is recorded and the non-canonical exemplars are flagged as legacy rather than harvested as rules.