ARchetipo

Runs the ARchetipo plan-to-implementation pipeline autonomously until the selected backlog specs reach REVIEW. Accepts no argument for every eligible spec, one EP-XXX code for an epic, or one US-XXX code for a single spec. Requires a fresh isolated worker for every planning and implementation phase. Use when the user asks to run everything, implement the backlog, process an epic autonomously, or autopilot one or more specs end to end.

Implements a planned spec by executing its technical implementation plan. Selects a PLANNED spec (passed as argument or auto-selected by priority), loads its implementation plan, and orchestrates Ugo, Mina, and Cesare to write code, tests, validation, and code review. The connector (configured in .archetipo/config.yaml) determines where specs and plans are read from and where status updates are written. Use this skill whenever the user wants to implement a spec that is already planned and ready for development, start coding a planned backlog item, or execute a sprint task from backlog. Do not use it for discovery, backlog creation, or planning work when the spec or implementation plan does not yet exist.

Conducts product inception and generates a PRD covering vision, personas, MVP scope, technical architecture, and functional requirements. Use whenever the user wants to define a new product, explore a product idea, scope an MVP, identify users and personas, or set up product vision — even if they do not explicitly ask for a PRD. Also triggers on Italian variants like "definire il prodotto", "idea di prodotto", "documento di prodotto".

Creates a detailed technical implementation plan for a spec. Use this skill whenever the user wants to plan a spec, break down a feature into technical tasks, create an implementation plan, do sprint planning, prepare a spec for development or estimate a feature. Also triggers on requests like "plan this", "break this down", "what are the tasks for this spec", or "how would we build this". The spec can be passed by code (e.g., US-005) or as a free-text description — the skill handles both automatically.

Facilitates the human acceptance gate for a spec in REVIEW status. Presents the delivered increment and its affected Wiki pages (acceptance criteria, diff, tests, documentation state and issues), records and presents a demo video for filmable specs, collects one informed human verdict, and either approves both the increment and ready Wiki knowledge (transition to DONE, with worktree integration when enabled) or sends it back with structured rework feedback. The connector (configured in .archetipo/config.yaml) determines where specs are read from and where status updates are written. Use this skill whenever the user wants to review, accept, approve, or reject a delivered spec, or to decide what happens to work that is waiting in the REVIEW column. Do not use it for code-level review during implementation (that is Cesare's job inside archetipo-implement) or for planning work.

Creates the initial product backlog from a PRD, or appends new specs to an existing one. Use whenever the user asks for a backlog, epics, specs, user stories, or wants to add a single feature — even if the backlog does not yet exist.

Bootstrap, query, ingest, refresh, review, and lint ARchetipo's codebase-first DDD Wiki. Use for mapping an existing repository into domains and candidate bounded contexts, locating domain code, maintaining living project knowledge, or answering project questions with bounded context.

Install ARchetipo on Hermes and manage ARchetipo projects through Hermes Projects and Kanban. Use it to install or update the ARchetipo CLI and workflow skills, create or clone a software project, switch or list projects, inspect project status, or queue one backlog spec on its project board for autonomous plan and implementation up to REVIEW. ARchetipo remains the source of truth for product workflow; Hermes Projects and Kanban provide the project registry and durable execution queue. Do not use this skill for product discovery, planning, implementation, or review directly — load the corresponding archetipo-* workflow skill instead.

Create isolated frontend mockups and visual prototypes inside docs/mockups. Use this skill when the user asks for mockups, UI concepts, visual explorations, prototype pages, landing page concepts, dashboard concepts, or design references for future implementation. Do not use this skill to implement, restyle, or refactor the real application source code.