After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and stack reference docs. More immediately actionable than ADRs (which explain why).
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "create-control-manifest" with this command: npx skills add sadowskr/skillsmp-sadowskr-sadowskr-create-control-manifest
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Guided, section-by-section authoring of the master architecture document for the product. Reads all design specs, the systems index, existing ADRs, and the stack reference library to produce a complete architecture blueprint before any code is written. Stack-version-aware: flags knowledge gaps and validates decisions against the pinned stack version.
Reviews a design spec for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.