harvest-dev-architecture

Extracts real coding conventions from completed code blocks into a reusable dev-architecture skill.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Workers on a codebase keep reinventing conventions because the project's real patterns — module layout, naming, test shapes, presenter/persistence structures — exist only implicitly in the code. This Skill harvests those stabilized conventions from the code of completed blocks and generates a dev-architecture skill that every future worker dispatch loads as architecture memory. ## Core Features & Use Cases - Convention harvesting from real code: Reads only the DONE blocks' code to extract layout, naming, test patterns, per-block-type patterns, and toolchain quirks, each backed by 1-2 golden exemplar files cited by path. - Conflict resolution as decisions: 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. - Authored-doc reconciliation: Grounds or refreshes a prescriptive dev-architecture doc written before the first domain wave, updating the same memory the profile points at rather than forking a second one. - Use Case: After the first green wave of a mismAgent build, run the harvest to generate <side>-dev-architecture/SKILL.md in .claude/skills/ (or .agents/skills/), then point sides.<side>.dev_architecture in the profile at it so the next worker dispatch loads it. ## Quick Start Ask the agent to harvest the dev-architecture conventions from the completed blocks of the active profile's side and generate the dev-architecture skill.

Frequently Asked Questions about 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 of the side is green. It reads only the DONE blocks' code, extracts conventions per dimension with golden exemplar files, presents a summary for confirmation, then writes the skill and updates the profile.

When should I harvest architecture conventions from a codebase?

Harvest after a slice is green, not after a single block — one block is anecdote, a slice is a pattern. Also re-run it when workers start reinventing conventions, since the harvest is regenerable from the code as it currently exists.

What is the difference between descriptive and prescriptive dev-architecture?

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.

Can one dev-architecture memory be shared across multiple deploy sides?

Yes. The memory attaches to the codebase, not the deploy role. Sides sharing one domain codebase get a single shared memory, with the profile's dev_architecture field for every such side pointing to the same value.

What happens when the code contains two competing patterns?

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.