Imported from brendandower90/ai-agent-bootstrap (AGENTS.md). Install upstream with npx skills add brendandower90/ai-agent-bootstrap. Copyright stays with the author.

Agentic Development Bootstrapper Agent Rules

Purpose

This repository is a reusable bootstrap pack for planning and workflow scaffolding. Use it to generate project-level documentation and agent workflow files for another repository.

IMPORTANT!

Never use the phrase "You're absolutely right!" in any response. Do not use the phrase "I understand" or similar phrases that imply empathy or understanding. Avoid being overly agreeable or giving excessive praise. Focus on providing clear, concise, and informative responses.

Prioritize tool use and terminal commands over MCP servers.

DO NOT modify the EULA or license agreement at the top of files.

Core Path Rule

Treat this repository, or any copied location such as .agents/bootstrap/, as the home of the prompt pack only.

When using these prompts inside another repository:

• create README.md, AGENTS.md, plans/, and tasks/ at the parent repository root
• create .agents/skills/ and related workflow assets under the parent repository's .agents/ directory
• do not generate project planning files inside .agents/bootstrap/ unless the user explicitly wants that nonstandard layout

Expected Workflow

1. Start with bootstrap-project.md when the user wants a new project scaffold or early planning workflow.
2. Start with bootstrap-feature.md when the user wants to add a feature workflow inside an existing repository.
3. Ask only the critical clarifying questions needed to lock scope, platform, delivery order, and planning depth.
4. Propose the planning set, task structure, and workflow files before generating them.
5. Generate planning documents before generating tasks.
6. Generate AGENTS.md, README, and skills after the planning and task structure are clear.
7. Stop after the bootstrap scaffold unless the user explicitly asks to continue into implementation.

File Intent

• bootstrap-project.md: entry point for the full bootstrap flow
• bootstrap-feature.md: entry point for feature bootstrap in existing repositories
• prompts/create-prd.md: generate or refine plans/prd.md
• prompts/create-planning-set.md: generate the rest of plans/
• prompts/generate-tasks.md: create tasks/tasks-master.md plus supporting task files
• prompts/create-repo-instructions.md: generate the target repository's AGENTS.md
• prompts/create-readme.md: generate the target repository's README.md
• prompts/create-project-primer-skill.md: generate .agents/skills/project-primer/SKILL.md
• prompts/create-bootstrap-build-skill.md: generate .agents/skills/bootstrap-build-system/SKILL.md

Editing Rules

• Keep prompts reusable across project types unless the user asks for a narrower template.
• Prefer explicit path wording whenever a prompt mentions output files or directories.
• Keep generated planning files aligned with each other and with the task system.
• Do not silently mix prompt-pack storage paths with output paths.
• Keep README content human-facing and prompt files instruction-facing.

Validation

• Re-read README.md before editing it because it may have changed independently.
• If a prompt is updated to add a new output type or workflow rule, update related prompts and the README in the same change when practical.
• Check for contradictory path guidance after edits, especially around .agents/bootstrap/, plans/, tasks/, README.md, and AGENTS.md.