Use for implementation-style tasks that modify code, files, pages, or project structure. Inspect first, then output an approval-first execution contract with atomic slices, red lines, green tests, acceptance ladder, commit plan, target artifacts, and a white-box acceptance YAML bridge. Do not edit files.
Use only after a checklist or atomic slices have been explicitly approved. Execute approved slices under the current run mode, preserve atomic discipline, verify, archive one commit per slice, report git state, package evidence for review, and stop on blockers or replanning needs.
A prompt package for creating a fresh auditor role under the Seven-Stars protocol. It defines the auditor’s identity, responsibilities, evidence boundaries, and limits, but does not perform the audit itself.
Route host-native plan/ask modes into Cyber-Ming contract lifecycle hooks. Use when a user asks to plan, execute, continue, take over, or when host plan mode should become an Atomic Execution Contract instead of free-form agent planning.
A workflow for carrying out coding work after the user explicitly activates free development mode. It allows pragmatic direct execution while keeping scope, safety boundaries, and engineering discipline explicit.
Parent policy layer for approval-first coding workflows under both plain and imperial registers. Defines non-negotiable constraints, not the primary auto-trigger workflow.
Read-only succession and handover briefing skill. Use when starting a fresh session, recovering from context decay, taking over an existing codebase, or needing a concise evidence-based project snapshot from git history, docs, and mainline code.
Use when the real uncertainty is operational and a full implementation plan would be fake confidence. Design and run the smallest probe that can surface the real red light, define the expected green light, and package the result for the planning layer.
★not rated 56 4mo agoA51 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: