MicroHard

Build a kanban board, status board, priority matrix, or project stage board as a .canvas file written directly to the Obsidian vault. Use when the user says build a board, create a kanban, make a status board, set up a project board, visualize the stages, or make a board for.

Turn any idea, topic, problem, or brainstorm into a radial mind map .canvas file written directly to the Obsidian vault. Use when the user says mind map this, map out, visualize this idea, make a mind map of, branch this out, or create a thought map.

Turn any system, architecture, workflow, or set of component relationships into a diagram .canvas file written directly to the Obsidian vault. Use when the user says diagram this, map the architecture, visualize the system, draw the flow, create a system map, map the components, or diagram how this works.

Create a new LLM Wiki domain from scratch — scaffolds the full directory structure, co-designs the schema, and prepares the wiki for first ingest. Use when the user says 'create a new wiki domain', 'init a wiki', 'set up a wiki for', 'start a new wiki', 'new domain wiki', or 'initialize lw'.

Ingest a new source into a domain wiki — reads the source, discusses key takeaways, then updates all affected wiki pages, the index, and the log. Use when the user says 'ingest a source', 'add an article to my wiki', 'add a book chapter', 'ingest a transcript', 'add a course module', 'update my wiki with', or 'process a source'.

Query the LLM wiki — ask questions and get answers synthesized from your own wiki pages, with citations. Valuable answers can be filed back as synthesis pages. Use when the user says 'query the wiki', 'ask my wiki', 'what does the wiki say about', 'search the wiki', 'find in my wiki', or 'cross-domain search'.

Run a health check on a domain wiki — finds contradictions, orphan pages, stale claims, missing pages, broken cross-references, and knowledge gaps. Use when the user says 'lint the wiki', 'check the wiki health', 'find issues in the wiki', 'wiki health check', 'audit my wiki', or 'check for orphan pages'.

Review and update a domain wiki's schema as the domain matures — audits the current schema against actual wiki structure, proposes changes, and applies approved updates. Use when the user says 'update the wiki schema', 'evolve the schema', 'fix wiki conventions', 'restructure the wiki', 'schema drift', or 'update naming conventions'.

Use when starting to build any new MicroHard artifact — skill, agent, module, workflow, or template. Converts a raw idea into a structured artifact brief. Trigger phrases: "build a new skill", "create a module", "new agent", "meta-skill", "ms brief", "engineer a skill", "I want to build something", "create something new", "add a skill".

Use when the artifact brief is approved and you need to design the full file structure. Reads artifact-brief.md and produces artifact-blueprint.md — complete directory tree, per-file content plan, and ordered build sequence. Trigger phrases: "ms blueprint", "design the structure", "architect the skill", "plan the files", "structure the module", "blueprint the skill".

Analyze vault knowledge graph topology — link density, isolated nodes, MOC coverage, cross-layer gaps. Use when the user says audit the graph, check vault connections, analyze vault links, graph audit, or check knowledge graph.

Full vault health audit — reads every note and produces a structured health report. Use when the user says scan the vault, vault health check, run health scan, audit the vault, or check vault health.

Route unfiled and misplaced notes to their correct vault sections. Use when the user says triage the inbox, route unfiled notes, file my notes, triage notes, or sort the inbox.

Audit vault tags and frontmatter, find drift, and apply corrections. Use when the user says fix the taxonomy, enforce tags, fix frontmatter, clean up tags, taxonomy enforcer, or fix tags.

Generate Obsidian Bases (.base files) for live database views of vault data. Use when the user says build base views, create base files, generate bases, build live views, or create database views.

Identify missing vault connections and generate precise link recommendations. Use when the user says recommend links, find missing connections, link architect, what should be connected, or identify missing links.

Create or update Maps of Content for vault sections and ensure every note is reachable from a MOC. Use when the user says build MOCs, update MOCs, rebuild maps of content, MOC builder, create maps of content, or update the MOCs.

Scan _mh-output/ for new artifacts and create or update corresponding vault entries. Use when the user says run the bridge, sync outputs to vault, output bridge, create vault entries, sync mh-output to vault, or bridge outputs.

Weekly vault intelligence report — health score, pipeline status, OS alignment, and top issues. Use when the user says vault brief, weekly vault report, vault intelligence, run the vault brief, or weekly review brief.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Use when defining MicroHard content pillars, building a content calendar, drafting posts, or reviewing content performance.

Use when optimizing MicroHard platform profiles (Upwork, Fiverr, LinkedIn) or planning activity to generate inbound leads from these platforms.

Use when assessing whether an inbound or outbound lead is worth pursuing — before a proposal is written or significant time is invested.

Use when managing follow-up on sent proposals — scheduling touches, writing follow-up messages, handling responses, and closing out stale leads.

Use when writing a proposal for a qualified lead — scoping the engagement, pricing the work, and drafting the proposal document.

Use when evaluating a new job posting. Qualifies a freelance job posting with a GO/NO-GO decision and scored card. Trigger phrases: "qualify lead", "score this job", "should I apply", "fl qualify", "lead qualifier".

Use when a lead has passed qualification. Deep-reads a job post and generates the Project Intelligence Document (PID) — the central artifact for the entire proposal chain. Trigger phrases: "analyze project", "build PID", "fl analyze", "project analyzer", "deep read this job".

Use when building the visual board for your Loom video. Generates a tool-agnostic visual board content specification from the narrative spine and PID. Works with any visual tool (Miro, FigJam, Notion, Canva, etc.). Trigger phrases: "build dashboard", "board spec", "fl dashboard", "visual board", "build the board".

Use when scripting your proposal video. Writes the 3-minute Loom video script. Hard 420-word ceiling. Opens with the client's situation, not your name. Trigger phrases: "write loom script", "video script", "fl script", "loom script", "write the script".

Use when the PID is complete and ready to propose. Builds the narrative spine and positioning angle from the PID. The strategic foundation for the entire proposal. Trigger phrases: "build narrative", "proposal architect", "fl architect", "position this proposal", "narrative spine".

Use when packaging the final proposal for submission. Assembles the complete proposal package from all upstream artifacts. Mode-aware: works with all artifacts, spine only, or PID only. Trigger phrases: "assemble proposal", "build proposal", "fl assemble", "proposal assembler", "package the proposal".

Use when a client responds with pushback, questions, or a counter. Handles client objections after proposal submission. Classifies the objection type and generates a calibrated response. Trigger phrases: "handle objection", "client pushed back", "fl objection", "they said the price is too high", "respond to client".

Use when a contract is signed and the engagement begins. Generates the full client onboarding kit after contract signing — kickoff document, intake questionnaire, and first-week plan. Trigger phrases: "onboard client", "kickoff kit", "fl onboard", "client won", "contract signed".

Use when sending any update to an active client. Generates proactive client status updates, milestone check-ins, and blocker communications during project delivery. Trigger phrases: "send update", "client update", "fl deliver", "milestone checkin", "project update".

Use when a project is delivered or 30/60/90 days post-close. Generates post-delivery review requests and re-engagement pitches. Cultivates 5-star reviews and seeds the next engagement. Trigger phrases: "request review", "re-engage client", "fl retain", "ask for review", "close the project".

Use when the artifact blueprint is approved and you are ready to generate all files. Reads artifact-blueprint.md and engineers every file one by one — generates content, shows for review, then writes to disk on approval. Trigger phrases: "ms build", "build the files", "engineer the skill", "start building", "write the files", "generate the skill", "implement the blueprint".

Use when a build is complete and needs quality validation. Validates every built file against MicroHard conventions — naming, frontmatter, I/O contract accuracy, step linkage, completeness. Produces a validation report with PASS/FAIL per check. Trigger phrases: "ms validate", "validate the skill", "review the build", "check the files", "quality check", "ms review", "validate the build".

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

Lossless LLM-optimized compression of source documents. Use when the user requests to 'distill documents' or 'create a distillate'.