aiwy-lock

Lock a selected design phase and update decisions.md and manifest.json.

Updated May 6, 2026
One-click install
npx skills add https://github.com/TsukimiRini/moyo-skills --skill aiwy-lock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwy-lock
Source: https://github.com/TsukimiRini/moyo-skills/tree/main/aiwy-lock
Command: npx skills add https://github.com/TsukimiRini/moyo-skills --skill aiwy-lock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of keeping an AI 文游 design process consistent by letting you formally checkpoint a specific phase so later work must align with the decisions already made.

Core Features & Use Cases

  • Phase checkpointing: Locks one of the design phases—concept, characters, world, gameplay, interfaces, or assets—so its artifacts become authoritative.
  • Consistency guardrails: Ensures downstream work stays consistent with the locked phase and clearly prompts an explicit unlock when changes are needed.
  • Workflow delegation: Hands off the full semantics to the aiwy-design workflow and records the lock via scripts.

Quick Start

Run /aiwy-lock concept to review and confirm the concept phase, then lock it as the single source of truth.

Frequently Asked Questions about aiwy-lock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lock a design phase to make it authoritative in an iterative workflow?

To lock a design phase, you run a lock command like `/aiwy-lock concept` to review artifacts, execute the lock script, and update `decisions.md` and `manifest.json`. This checkpoints the phase so its artifacts become the single source of truth for downstream work.

What is phase checkpointing in project management and when do I need it?

Phase checkpointing in project management is the process of freezing a specific design stage—like concept, characters, or world—so its artifacts become authoritative. You need it during iterative design workflows when you want a phase to become definitive and ensure downstream consistency.

How do I keep downstream work consistent with earlier design decisions?

You keep downstream work consistent by locking a phase to establish consistency guardrails. Once locked, downstream work must align with the authoritative artifacts, and the system clearly prompts an explicit unlock if changes are needed.

What happens if I need to modify artifacts after locking a phase?

If you need to modify artifacts after locking a phase, the consistency guardrails require an explicit unlock. The lock ensures downstream work stays consistent, so any necessary changes to the authoritative phase must be deliberately unlocked before modifications can proceed.

Do I need the aiwy-design workflow to use phase locking?

Yes, you need the aiwy-design workflow to use phase locking because the skill hands off the full semantics to it. The locking process records the lock via scripts within the aiwy-design workflow environment.

Can I lock any design phase in my project?

You can lock specific design phases in your project including concept, characters, world, gameplay, interfaces, and assets. The skill applies checkpointing to these phases during iterative design workflows when you want a phase to become definitive.