AGENT SKILL

init

Paved command paved.init. Initialize Paved and prepare repository context and verification; offer a project-local app verification guide when a runnable user interface is present. Use when setting up Paved in a repository that is not initialized.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
init
description
Paved command paved.init. Initialize Paved and prepare repository context and verification; offer a project-local app verification guide when a runnable user interface is present. Use when setting up Paved in a repository that is not initialized.

03 SKILL.md 正文

<!-- Generated by Paved plugin paved@2.29.0 from paved.init; edit Paved Core instead. -->

Paved init command (paved.init)

Initialize Paved and prepare repository context and verification; offer a project-local app verification guide when a runnable user interface is present. Use when setting up Paved in a repository that is not initialized.

Input: No arguments. Output: Initialization result, detected adapters, lifecycle state, diagnostics, and an optional app verification guide offer. Required lifecycle: UNINITIALIZED Required context: .paved/manifest.yaml, repository evidence Required capabilities: none declared Allowed side effects: .paved/ initialization state, generated project context, managed AGENTS.md block, .paved/skills/verify-<app>/ only after the user accepts the offer

Execution contract

  1. Invoke node "${CLAUDE_PLUGIN_ROOT}/scripts/paved.mjs" init --json from the repository root, passing the user's command inputs as supported CLI arguments. The launcher loads the pinned project-local runtime and returns the canonical structured result. Always run it from the repository being worked on, never from the plugin directory.
  2. Follow the structured result's status, diagnostics, evidence, and next action. When data.remediation names a Paved command, run it right away, present any decisions it returns, then repeat the original command. Stop only when the runtime blocks on something it cannot remediate.
  3. After a successful initialization, inspect repository evidence for a runnable user-facing application or command-line interface. If one exists and no matching .paved/skills/verify-* guide exists, activate core.testing.app-verification and create the project-local guide as part of initialization. If no runnable interface is present, finish initialization without creating one. Never overwrite an existing project guide; mention that app-verification can update it when requested.

Failure behavior

  • Existing Paved state is never reset.
  • Invalid partial state fails with diagnostics.
  • Package acquisition and runtime activation require verified integrity.
  • If a required ToolImplementation or runtime is unavailable, stop and explain the missing prerequisite. Never infer or execute a command from repository scripts.
  • Do not edit human-owned Paved state or bypass lifecycle, ownership, approval, or verification gates.

Conversational contract

  1. Invoke the command. If it returns "status": "awaiting_input", it is waiting on the user.
  2. Present every decision in decisions[] to the user: what Paved detected, what remains to decide, why it matters, the options, Paved's recommendation and its evidence.
  3. Collect the user's answer. Do not answer on their behalf.
  4. Resume the same command with --answer <decision-id>=<value> --answered-by <identity>, repeating --answer once per value for a multi-choice decision.
  5. Present the result.

Follow core.decisions.decisions for the full interaction protocol and its prohibitions.

04 同仓库更多 Skills