Stip Bootstrap

stip-bootstrap

Prepare the project once; do not run a full audit before every feature.

1. Inspect the repository instructions and enough evidence to identify project intent, current structure and delivery context. For a new repository, clarify the minimum intent before inventing foundations. For an existing one, preserve conventions and distinguish observed behavior from intended behavior.
2. Run python3 /scripts/setup_stip.py --root . This prepares the workflow, appends one bounded block to AGENTS.md, adds an @AGENTS.md import to CLAUDE.md while preserving existing instructions, and copies all bundled domain packages into the project as available extensions. It does not initialize Git, choose a stack, certify maturity, or select extensions for any change.
3. Populate .workflow/project.md with intent, map, actual commands and relevant evidence. Classify each relevant area as established, inferred, incomplete, missing or not-applicable. Inspect source as well as docs. An interface may have an undocumented component system; cloud-only work needs no design assessment.
4. Review existing AGENTS.md rather than replacing it. Resolve contradictions explicitly. Keep existing extension configuration; register custom paths only when the package exists. Availability does not imply selection. All 28 domain packages are bundled in this skill under assets/extensions/. Setup preserves already configured packages, customizations, and disabled entries. Do not read the entire catalog: identify relevant domains from project evidence; stip-explore selects and reads only the references needed for a change.
5. Report what was created, preserved, inferred and still unknown. Subsequent feature work starts at stip-explore; rerunning bootstrap preserves current changes and project notes.

Do not create an empty example feature. The first real stip-explore creates its own folder. Do not claim a project is production-ready merely because bootstrap succeeded.

Runtime

Use scripts/setup_stip.py above for normal bootstrap, including the bundled catalog. The low-level workflow.py bootstrap command only creates workflow metadata and remains available for core-only fixtures.

Use the Python runtime bundled with this skill, independent of the current directory:

python3 /scripts/workflow.py --root  

Python 3.10+ and Git are required for implementation and archive. Run --help or --help for exact arguments. The runtime is offline and never installs tools. System/developer instructions, current user intent and environment permissions remain authoritative.

For explicit OpenCode /stip-* command files, run python3 /scripts/install_opencode_commands.py --destination /.opencode/commands when requested. Use ~/.config/opencode/commands instead for a requested global installation. This installs wrappers that load the existing skills; it does not duplicate their procedures.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: BRYANN2K
• Source: BRYANN2K/stipulate-skills
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.