---
name: app-primer-zero-stinger
description: "Prepare an app's private Library, current state, contracts, complete schema baseline and bounded wave handoff before implementation. Use for app-primer-zero or foundation preparation."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, Codex, Cowork; ZCode uses discovered skills. Core Wasp Nest methods required; Python 3.9+ for optional planning validation."
metadata:
  hive-tier: standalone
  domain: app foundation preparation
  core-dependency: wasp-nest-core
---

# App Primer Zero Stinger

## Purpose

Prepare any new or partial repository for a later build: organize private Knowledge, establish actual current state, draft the foundation PRD/contracts/schema, qualify reuse boundaries and deliver a wave-plan handoff. This is a direct-use composition skill, not a new specialist Drone or an implementation launcher.

## When to use

- "Run app-primer-zero", "prime this app", or "prepare this repo before the build".
- "Set up the Library, sort the docs, and give me the state of the union".
- "Create the contracts/seams/schema foundation and a bounded wave handoff".

## When not to use

A bounded feature/bug fix belongs to Pest Controller and its specialist; execution of an approved feature PRD belongs to Smoke It. Existing current-state narration alone belongs to Knowledge. Do not turn preparation into unsolicited implementation, provider setup or deployment.

## Procedure

1. Read [the workflow map](README.md) and [intake/authority](guides/00-intake-and-authority.md). Record current scope, actual baseline, dirty owners, decisions, CI preference and supplied versus qualified harness capabilities.
2. Resolve [core dependencies](references/core-dependencies.md). Load Pest Controller before routing; use Get Started, Knowledge, Library and Contract Writing for their owned phases. Do not duplicate their rules or claim a native role exists without the capability.
3. Follow [inventory/Library](guides/01-inventory-and-library.md). Organize source docs only within authorized scope; preserve historical bodies and links; produce truthful current-state evidence.
4. Follow [contracts/schema](guides/02-contracts-and-schema.md). Draft the foundation PRD using the repo's number/lifecycle, full source-field ledger and native schema reference. Keep exact contract terms Draft until owner acceptance; selected providers are a separate decision.
5. Follow [reuse/waves](guides/03-reuse-and-waves.md). Pin specific donor modules, adapt scope/provider/runtime assumptions, and create contract-first waves with one integrator and exclusive paths. Count every overlapping worker and coordinator overhead within the effective ceiling; use explicit serial preparation when threading is unavailable.
6. Follow [verification](guides/04-verification-and-delivery.md). Validate structural artifacts and report actual evidence; run applicable ordered reviews, then deliver a coordinator starter and bounded worker brief. A valid planning artifact is not runtime or approval proof.
7. Stop at the preparation handoff unless the user separately authorized execution. Preserve current approvals within their exact scope. Follow the actual deadline/retry rules and return the six-field report.

## Resources

The templates and fictional example are indexed in [README.md](README.md). Run `scripts/validate_handoff.py` on a JSON handoff for graph/capacity/pin/path errors; `scripts/test_validate_handoff.py` tests that helper. Neither executes work nor verifies human authorization. Read [threading](references/threading.md) when installing or packaging and [distillation](references/research/distilled-app-primer-zero.md) when checking a domain claim.

## Critical Directive

- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
  - [Core method resolver](references/core-dependencies.md): Get Started, Knowledge, Library, Contract Writing, Security, Quality and repository-health.

## Ship Gate

Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so.