AI Spec Authoring & Git Workflow FAQs

Question 1

What files does the 'propose' command generate?

Accepted Answer

The command generates three distinct files in a dedicated feature directory: proposal.md (high-level overview), spec-delta.md (technical requirements), and tasks.md (implementation breakdown).

Question 2

What is the 'Specs as Code' philosophy?

Accepted Answer

It is the practice of treating documentation with the same rigor as code, where changes are proposed via branches, reviewed through Pull Requests, and merged only after approval.

Question 3

How does the 'update' command handle PR feedback?

Accepted Answer

It uses the GitHub CLI to fetch all comments from a specific PR, then uses Gemini AI to analyze those comments against your local files to produce a synthesized, actionable summary of recommended changes.

Question 4

Does this skill replace manual code reviews?

Accepted Answer

No, it is designed to assist the process. It automates the drafting and the synthesis of feedback, but the final strategic decisions and design refinements remain with the developer.

Question 5

What are the prerequisites for using this skill?

Accepted Answer

You need a project initialized with the AgenticDev structure (docs/specs/ and docs/changes/), along with the GitHub (gh) and Gemini CLI tools installed and authenticated.

AI Spec Authoring & Git Workflow

Key Features

Use Cases

AI Spec Authoring & Git Workflow

Key Features

Use Cases