owners-vision
Check project readiness immediately after installing or updating this skill, complete authorized setup, and review implementation against the owner's vision with a subagent whenever supported; append accomplishments only with explicit authorization.
Ammar Al Balkhi · 站主发布
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add https://github.com/ammarbalkhi/owners-vision/tree/b52cc4df000fcd8e1c33598ef5373b0ad45d5c8b/owners-vision --skill "owners-vision"技能说明
name: owners-vision description: Check project readiness immediately after installing or updating this skill, complete authorized setup, and review implementation against the owner's vision with a subagent whenever supported; append accomplishments only with explicit authorization.
The Hand of the Owner
Protect the owner's fixed product destination and every owner-locked accomplishment. Use before new implementation and when the owner explicitly authorizes an accomplishment addition. This skill grants no authority to implement, commit, publish, or change a project's direction.
Owner's Vision is the owner's authoritative destination and recorded accomplishments. The Hand of the Owner is the checking role defined here; its reviewer and verdict cannot change that authority.
Installation, updates, and project readiness
After any agent-managed installation or update, read the installed copy and check this project's readiness before reporting completion. A request to use the skill also starts with this check. Do not wait for the next implementation request to disclose missing setup. File installation alone does not establish the project's vision or mandatory Hand rule.
Inspect the governing rules, approved vision, companion lock, accepted digest, and required Hand instruction. If initial setup is incomplete, follow setup and automatically finish the work covered by existing, applicable owner approval. Handle files and hashes for the owner. If approval is missing or setup was explicitly stopped, report what is missing and ask one short question to authorize or resume it; do not repeat an answered question. An update request alone does not cancel a previous stop, read-only, or explicit install-only restriction.
For a project without a vision, use the first-use invitation to gather the desired end result and details, with the option to provide a Markdown (.md) vision or plan. Use information already supplied before asking for more.
Report installation status and project readiness separately and briefly: ready for Hand checks, setup incomplete with its missing prerequisite, or blocked by an established integrity failure. Verify a complete binding without changing it. Never treat a failed established lock as initial setup or regenerate it to obtain readiness. A file-copy installer may not execute these instructions; the agent handling installation or update must perform this handoff.
Incomplete setup does not reopen an owner-approved destination. On a conflicting implementation request, return PAUSE with the conflict and missing prerequisites; do not propose replacement wording. If the owner says wait or stop, preserve the current state. A missing or mismatched previously established lock is a verification failure, not a fresh-setup opportunity.
Project authority and lock
Read the current project's governing rules to identify its owner, exact vision file, companion SHA-256 lock, and independently accepted digest. Use that project's binding; never substitute another project's vision, a template, or remembered wording. Names such as OWNER_VISION.md and OWNER_VISION.sha256 are examples, not mandatory filenames.
Read the entire vision, including appended checkpoints. Verify its exact bytes against both the companion lock and the accepted digest in the project's governing rules. Missing, unreadable, ambiguous, or inconsistent authority requires PAUSE. Never regenerate a lock to make a failed check pass.
For a read-only integrity check, use scripts/check_vision.py:
python check_vision.py --vision VISION_FILE --lock LOCK_FILE --expected-sha256 ACCEPTED_DIGEST
The helper verifies integrity only. It cannot grant a Hand PASS or owner authorization.
Required alignment review
Before implementation:
- Verify the current vision and lock. Read the exact proposed work, what the user will do before and after it, and what the user will see when it finishes. A proposal too vague to compare requires PAUSE.
- Subagent review has priority and is required whenever supported. Check the environment's available or discoverable reviewer capabilities before declaring it unsupported. Launch one fresh read-only reviewer or oracle subagent and wait for its returned review; do not choose same-session review for convenience. Give it a fresh context containing the exact locked vision, digest, proposal, user-visible result, and relevant evidence. It must not edit, implement, invent an exception, or act as owner authority. Discovering a reviewer tool or reusing an earlier review does not complete this step.
- If subagents are unsupported, perform a dedicated read-only review yourself in this same session. Re-read the verified vision and compare every part of the proposal with its destination, checkpoints, and acceptance limits. This fallback needs no extra owner approval, new session, or separate CLI call. It is a same-agent review, not an independent review.
- In either mode, answer: Does every part of the proposed work fit the locked Owner's Vision and preserve its achieved checkpoints without changing or straying from them? Check the conclusion against the actual proposal and evidence. An unresolved conflict or inconclusive review requires PAUSE. A failed integrity check stops the gate before review. If a supported subagent was launched but its review failed or did not return, PAUSE; do not use the fallback to bypass that failure or an adverse review.
An implementation's success does not justify rewriting the owner's destination or lowering an achieved checkpoint.
On a conflict, report it and stop implementation. Do not offer to replace, weaken, or renegotiate the vision to make the proposed work fit. Record the method and assessment in the session's normal record. For subagent review, also preserve the actual invocation and returned result; never label a same-agent re
阅读完整来源 ↗