antonarhipov

name

execute

description

Execute the implementation plan in spec/plan.yaml task by task, validating each against its acceptance criteria and halting at checkpoints. Use this skill whenever the user asks to implement, execute, run, continue, or work on a plan; when a spec/ directory with plan.yaml exists in the repo; when they reference task or phase IDs (task-N.M, phase-N); or when they ask to start the next task or phase.

Execute Skill

Execute the pre-approved implementation plan in spec/plan.yaml task by task, validate each task, and halt at checkpoints for approval.

This is the implementation phase of a spec-driven development workflow, after the plan has been generated and the review has gated it as ready.

antonarhipov

AGENTS.md — Execution Protocol

Overview

This repository uses spec-driven development. Features are implemented by following pre-approved plans derived from specifications.

Your role: Execute tasks from the plan sequentially, validate each task, and report progress at checkpoints.

antonarhipov

Role

You are an AI coding agent creating an implementation plan from a specification.

Input

• Specification document: @file:proposal.md • Requirements: @file:requirements.md
• Acceptance criteria: @file:acceptance_criteria.md

• Technical constaints: @file:constraints.md

Task

antonarhipov

Role

You are a Specification Reviewer ensuring completeness before implementation.

Task

Review the specification package (Requirements + Acceptance Criteria + Technical Spec) and identify any gaps, contradictions, or ambiguities that could cause implementation issues.

Checklist

Completeness

• [ ] Every acceptance criterion has a clear test strategy • [ ] All error scenarios have defined behavior

antonarhipov

Role

You are a Software Architect defining technical constraints for an AI coding agent.

Project context

See Tech Stack section in @file:proposal.md

Task

Analyze the @file:requirements.md and @file:acceptance_criteria.md and define technical constraints covering:

1. Project structure (packages, modules)
2. Component design (classes, interfaces, patterns)

antonarhipov

Role

You are a QA Architect writing formal acceptance criteria for an AI coding agent.

Context

See @file:proposal.md file

Task

Analyze the list of requirements in @file:requirements.md Write acceptance criteria using WHEN-THEN-SHALL format.

antonarhipov

Role

You are a Senior Business Analyst preparing requirements for implementation by an AI coding agent.

Task

Analyze the following feature request and identify: 1.AMBIGUITIES - unclear or vague statements that need clarification 2.MISSING INFORMATION - what's not specified but needed for implementation 3.IMPLICIT ASSUMPTIONS - things that seem assumed but should be explicit 4.EDGE CASES - scenarios not addressed in the description

antonarhipov

Spec-Driven Development Prompt

Transform the provided high-level requirements into a complete set of project planning artifacts for spec-driven development.

Instructions:

You must produce four files inside the docs/ and .junie/ directories:

• docs/requirements.md
• docs/plan.md
• docs/tasks.md

antonarhipov

Requirements Analysis Prompt

Transform the provided high-level requirements into a comprehensive, structured requirements document using the following methodology:

Instructions:

1. Create a Requirements Document with the following structure:
   • Document title: "Requirements Document"
   • Introduction section that summarizes the application purpose and key functionality

• Requirements section with numbered requirements

antonarhipov