Claude Skills by dpaola2

Run pipeline Stage 2 (Architecture) for a project. Designs data model, API endpoints, migrations, and security scoping based on Pipeline Configuration in the conventions file.

Retrofit YAML frontmatter with pipeline timing metadata onto existing project documents that were created before timing was implemented.

Push the implementation branch and create a PR against the default branch with a generated summary from project artifacts.

Run pipeline Stage 1 (Discovery) for a project. Explores the target codebase to understand current state before designing changes.

Run pipeline Stage 3 (Gameplan) for a project. Produces the engineering spec from PRD + Discovery Report + APPROVED Architecture.

Run pipeline Stage 5 (Implementation) for a project milestone. Writes code to make Stage 4's failing tests pass.

Compute and display pipeline timing metrics for a project by reading YAML frontmatter from all project documents.

Detect the current pipeline stage for a work item and run the next stage. Handles approval gates by invoking /pipeline-approve.

Interactive approval review for pipeline checkpoints. Walks through the approval checklist and open questions for architecture proposals and gameplans.

Run the full pipeline autonomously for a work item. Chains stages with context isolation, handles approval gates via interactive interview or auto-approve.

Set up a repository for the agent pipeline. Auto-detects framework, stack, and directory structure, then writes the Pipeline Configuration section into the conventions file.

Generate a structured PRD from a WCP work item brief. Reads the work item body as input, produces a pipeline-ready PRD attached as a WCP artifact.

Run pipeline Stage 7 (QA Plan) for a project. Generates a comprehensive QA plan from all project artifacts after implementation is complete.

Generate a code quality report for a pipeline project by reading quality frontmatter from progress.md and optionally running fresh analysis.

Generate release notes from a Linear cycle — pulls completed issues, categorizes them, and formats the notes using the previous cycle's format as a template.

Run pipeline Stage 6 (Code Review) for a project. Reviews the full branch diff against conventions, security requirements, spec, and code quality. Produces a review-report.md with categorized findings and a verdict.

Run pipeline Stage 4 (Test Generation) for a project. Writes failing TDD test suites in the primary repo from the approved gameplan.