Manuals
Manuals64 pages

Manuals

Every root documentation file is rendered as a centered, readable manual page with consistent spacing and source provenance.

Taxonomy

Manual coverage by field

The generated library covers operating practice, authoring standards, runtime contracts, integrations, verification, and maintenance.

7Manuals
45Guides
12Reference pages
64Total docs
GUIDEAgent Library Integration GuideThis guide explains how MD capabilities connect to a separate agent library without duplicating the same ontology, prompt bodies, or governance rules in two places.→ GUIDEArchitecture GuideThis guide explains the suite as a set of cooperating layers. The architecture is designed to prevent a single oversized prompt from owning context, authority, research, execution,→ GUIDEAuto-Orchestration Runtime GuideThe automatic layer is a conditional compiler. It never loads all auto-prompts by default. It evaluates route-changing intent ambiguity, genuine skill need, missing capability, acq→ GUIDEAuto-Prompts and Conditional Routing GuideThe auto-prompt layer resolves a small set of recurring orchestration problems that should not be reimplemented inside every domain prompt:→ GUIDEBounded Loop Orchestration Guide`MD-197` can loop **any prompt, scenario, or exact skill**. The target is generic. The eligibility test—not the domain—decides whether looping is useful.→ REFERENCECapability ArchitectureThe suite uses control prompts, standalone investigations, standalone production or operations, independent gates, and genuine investigate→execute or brief→produce pairs. Pairing i→ GUIDECI and Testing GuideThis guide describes the deterministic checks that keep the suite coherent after prompt, schema, scenario, policy, skill, model, documentation, or runtime changes.→ GUIDEIdentity and Runtime Path GuideMission Directives exposes current, permanent capability identities and current agent skill destinations. The repository does not ship historical release maps, redirect tables, or → GUIDECompletion Criteria Guide`<completion_criteria>` is the contract that prevents a model or operator from confusing activity with completion. It answers:→ GUIDEContributor GuideThis guide explains how to change the suite without creating duplicate capabilities, weakening safety, breaking permanent identities, or allowing generated artifacts to drift.→ REFERENCECoverage IndexThe suite contains **257 prompts**, **32 genuine pairs**, **110 composite scenarios**, **27 department packs**, and **277 registered skills**. The supplied OpenCode snapshot contai→ GUIDECross-Platform Tooling Guide[Back to Mastery Manual](MD_MASTERY_MANUAL.md) · [Manual index](MANUALS.md)→ GUIDEDocumentation Site GuideThe static Astro site publishes the public documentation surface at `https://manojpisini.github.io/mission-directives/`. The source lives under `site/` and uses the checked-in HTML→ MANUALEvaluation ManualEvaluation determines whether the suite behaves as intended. File counts and valid frontmatter are necessary but do not prove model behavior, tool safety, or artifact quality.→ REFERENCEEvidence LanesEvery task uses one lane. The lane controls how facts, interpretation, and invention may appear.→ GUIDEExecutive Decision Rules GuideExecutive prompts take approved action. Procedure alone is insufficient because execution encounters conflicts, incomplete budgets, stale evidence, failed checks, and domain-specif→ GUIDEGeneric Skill Execution Guide`MD-196` is a universal typed adapter for **any exact installed skill**. It is not limited to design skills, personal skills, or skills already curated in `skill_registry.json`. Th→ REFERENCEGetting StartedMission Directives installs a command-line runtime globally and pins a complete operational copy inside each project. The project copy keeps routing behavior stable across global p→ GUIDEGitHub Actions Failure History and Pre-Push GuideThis guide records every failed GitHub Actions validation run through July 28, 2026, its root cause, durable correction, and prevention rule. GitHub Actions results are commit-spec→ GUIDEgstack Integration MatrixThe suite treats every gstack skill as an optional adapter. Its loaded schema is authoritative; the prompt system remains responsible for evidence, permissions, output contracts, a→ GUIDEMission Directives Installation and Project Integration GuideMission Directives 2.0 installs a global command and a pinned, project-specific runtime. The global package provides lifecycle commands. Routing inside an initialized project uses → GUIDEInstalled Runtime Payload GuideThis guide defines the boundary between a working-project installation and the Mission Directives source repository. `config/runtime_payload.json` is the machine-readable source of→ GUIDEInstalled Skills Inventory Guide`installed_skills_inventory.json` records a snapshot of skills detected in the user's OpenCode global skill directory. The supplied snapshot was normalized from the OpenCode global→ GUIDELocal Output Viewer GuideThe local viewer is a visual wrapper over existing generated files. It does not rename, rewrite, index, or duplicate outputs. The installed templates and CSS live in `.mission-dire→ GUIDELocal Skill Registration GuideThis guide governs skills created locally rather than installed from a reviewed remote repository. Local creation is a fallback for a genuine capability gap, not a shortcut around → GUIDELogging and Telemetry Guide[Back to Mastery Manual](MD_MASTERY_MANUAL.md) · [Manual index](MANUALS.md)→ MANUALManual Quality StandardManuals are operational interfaces, not decorative summaries. A manual is acceptable only when a reader can understand the system, perform the task, recognize failure, reproduce va→ MANUALManuals and GuidesThis index is the human navigation layer for the Mission Directives. The suite is machine-readable, but operators and maintainers should not have to reverse-engineer JSON files or → MANUALMission Directives Mastery Manual**Version:** 2.0.2→ GUIDEMigration GuideMigration moves only content proven to belong to an older managed Mission Directives installation. Generic project folders are not treated as owned merely because their names match→ GUIDEModel Routing GuideModel routing selects a model only when measured evidence supports the requested prompt, evidence lane, output contract, tools, and assurance profile.→ MANUALOperator GuideThis guide is for the person running the suite, approving actions, inspecting manifests, and deciding whether a run may progress.→ GUIDEPackaging and Release Guide`pyproject.toml` defines the public `mission-directives` package, Python 3.11 minimum, `mission-directives` console entry point, runtime dependencies, and `MIT OR Apache-2.0` licen→ GUIDEPair Authoring and Verification GuideA genuine pair separates non-mutating investigation from authorized execution. The split is justified only when the handoff improves safety, reviewability, parallelism, or output q→ GUIDEPlan Review and Exact-Twin Execution GuideThis guide defines the mandatory transition from a paired investigative planning prompt to its one authorized execution twin. The policy applies to every prompt whose frontmatter d→ GUIDEProject Cleanup and Uninstall GuideThe 2.0 uninstaller removes only a validated Mission Directives project installation and its managed guidance and ignore blocks. It does not infer ownership from common directory n→ GUIDEProject Config Guide`.mission-directives/project.json` is durable, agent-facing project knowledge. `.mission-directives/config.json` is system-owned installation and viewer configuration. Project Conf→ GUIDEPrompt Addition and Registration Guide**Purpose:** Add one new prompt to Mission Directives from a Markdown source file without manually editing every catalog, graph, fixture, routing table, or integrity receipt. **Can→ GUIDEPrompt Body Authoring GuideThis manual explains how to create or revise a prompt body that is precise, composable, least-privileged, machine-parseable, and verifiable. It supplements the normative `PROMPT_ST→ GUIDEPrompt Body Validation GuideThe suite validates prompt bodies separately from frontmatter, catalogs, scenarios, schemas, skills, and runtime state. This prevents a structurally complete catalog from hiding we→ REFERENCEPrompt Catalog**Prompt count:** **257**→ REFERENCEPrompt Engineering MethodsThe suite uses task-fit methods rather than adding every technique to every prompt.→ REFERENCEStructured Prompt Design StandardThis document defines the canonical body contract for every prompt in the suite. It is normative: prompt authors, transformation scripts, validators, scenario compilers, skill adap→ REFERENCEPrompt Suite ConventionsThis file defines suite-wide conventions that apply to every prompt, scenario, skill adapter, model adapter, runtime artifact, manual, and validator.→ REFERENCEDocumentation LibraryThe documentation library explains how to operate, author, validate, secure, and extend the prompt suite. It is organized by reader task rather than file age or generation order.→ REFERENCERecommended Skill StacksThese are the highest-value default stacks for this suite. Install only the exact skills needed for the current workflow, review the current source and audits, and keep native prom→ GUIDERecovery and Rollback GuideRecovery is a designed and verified capability, not a sentence in an action plan. This guide explains how consequential runs prepare, exercise, select, and verify rollback, roll-fo→ REFERENCEResearch BasisThe suite applies prompt-engineering techniques selectively according to task, model, risk, and output medium. No technique is treated as a universal incantation. The operating sta→ GUIDERoot Agent Guidance and MD Keyword Routing GuideThis guide explains how to connect a project repository's root agent-instruction files to the Mission Directives without copying prompt bodies into those files or overwriting human→ GUIDERouter Keyword Catalog and Scoring GuideThis guide defines the deterministic intent-routing vocabulary, scoring model, confidence behavior, diagnostics, and extension workflow. The runtime source of truth is `config/rout→ REFERENCERuntime Marker ProtocolRuntime markers give human-readable artifacts stable machine identifiers. They connect evidence, uncertainty, findings, actions, verification, and stops across prompts, tools, mode→ GUIDEScenario Authoring GuideA scenario is a reusable cross-capability execution route. It is justified when the same combination of evidence, planning, production, review, authorization, and verification recu→ GUIDESecurity Testing and Simulation BoundariesSecurity prompts are defensive capabilities for systems the operator owns or is explicitly authorized to test.→ GUIDESecurity Operations GuideThis guide applies to defensive security review, authorized simulations, exploit reproduction, model and agent security, incident response, OSINT, and security remediation.→ GUIDESkill Installation and Integration GuideInstall **only the exact skill needed**. Every command below uses the per-skill form; it does not install the full repository. Review the current source and audit results before in→ GUIDESkill RoutingSkills are optional execution adapters, not hidden prompt powers. The router probes availability, trust, and fit before selection; unavailable skills never block the native prompt → GUIDESkill Supply-Chain GuideThird-party skills can improve specialized work, but they are executable supply-chain dependencies. This guide defines how skills are discovered, locked, reviewed, tested, quaranti→ GUIDETelemetry and Observability GuideTelemetry makes routing, execution, verification, failure, and improvement observable without storing unnecessary sensitive content. It supports model selection, cost control, drif→ GUIDETemplate System Guide[Back to Mastery Manual](MD_MASTERY_MANUAL.md) · [Manual index](MANUALS.md)→ GUIDETool Policy and Authorization GuideAuthorization and tool selection are related but different:→ GUIDETroubleshooting GuideFor the complete GitHub Actions incident history, fixing commits, and required prevention checklist, see [GitHub Actions Failure History and Pre-Push Guide](GITHUB_ACTIONS_FAILURE_→ MANUALTUI and Operator Experience Guide[Back to Mastery Manual](MD_MASTERY_MANUAL.md) · [Manual index](MANUALS.md)→ MANUALUser ManualThis manual explains how to use the suite without reading all 257 prompts. It focuses on selecting the right outcome, setting honest authority, choosing an evidence lane, understan→ GUIDEVisual Assets Integration Guide`visual-assets` is a user-owned local skill for deliberate, editorially designed visual construction. It builds assets from primitives:→