ampa-project-setup

AMPA Project Setup Skill

Overview

Project environment setup for AMPA (see agent definition for role context and supported languages table). Covers language detection, package manager initialization, dependency installation, linting, testing, and SERENA MCP activation.

Use when starting work on a new project or onboarding to a project that lacks tooling. For per-task environment verification, see Step 3 of ampa-task-execution.

Prerequisites

1. Write access to the project directory
2. SERENA MCP available for activation
3. Know the target language (or be ready to detect it)

Instructions

Copy this checklist and track your progress:

1. Read this SKILL.md to understand the operations before executing.
2. Navigate to the project root and confirm write access.
3. Detect language — see Resources table. Record the result.
4. Init package manager — see Resources table. Verify with version command.
5. Install dependencies — see Resources table. Confirm zero errors.
6. Configure linting — see Resources table. For Python, also read ruff-configuration-patterns.md. Verify linter runs.
7. Setup testing — see Resources table. Run test suite once.
8. Activate SERENA — see Resources table. Verify with find_symbol.
9. Report setup status to AMOA confirming the environment is ready.

Output

• Initialized package manager, installed dependencies, linter config, test framework config, active SERENA MCP connection.

Error Handling

If any setup step fails, do not proceed to the next step. Report the failure to AMOA with the step name, error output, and the log file path. Wait for guidance before retrying.

Examples

• Input: New Python 3.12 project directory
• Output: uv init, deps installed, ruff configured, pytest ready, SERENA active

Resources

Document	Description
op-detect-project-language.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-initialize-package-manager.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-install-dependencies.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-configure-linting.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
ruff-configuration-patterns.md	When to Configure Ruff for a New Project, Standard ruff.toml Template for AI Maestro Programmer Projects, What Each Rule Set Does, What Each Ignored Rule Means, Per-File Ignore Patterns, Formatter Settings, How to Run Ruff, Customizing Ruff for Specific Project Types
op-setup-testing-framework.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-activate-serena-mcp.md	When to Use, Prerequisites, Procedure, Examples, Error Handling

Governance

This skill operates under the AI Maestro approval tiers — the escalation ladder Tier 0 (self-authority for in-scope work + DERIVED NPT/EHT tasks) → CHIEF-OF-STAFF → MANAGER → USER. See the ampa-prrd-trdd-kanban skill and ~/.claude/rules/trdd-approval-tiers.md for which transitions need approval. A MEMBER never self-approves its own releases — entering the release pipeline (publish/deploy) is USER/MANAGER-authorized, and the INTEGRATOR (not the MEMBER) owns the → complete flip.

Related

• ampa-task-execution — Next skill after project setup.