ls-agentic-prd-batch

Process ready PRD specs by priority and update statuses with verification outcomes.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-agentic-prd-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-agentic-prd-batch
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-agentic-prd-batch
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-agentic-prd-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates PRD batch processing to load ready specs, apply per-spec tasks, and update statuses, ensuring auditable workflows aligned with PRD_SCHEMA and external agent guides.

Core Features & Use Cases

  • Locate PRD/spec files in configured paths, exclude README/INDEX/SPEC-TEMPLATE, filter by front matter status, and sort by priority then date.
  • Update spec status to in-progress when processing starts; mark as done or blocked upon completion; ensure queue INDEX alignment when present.
  • Write outcome blocks including branch, commit SHA, changed files, verification steps, and rollback instructions; maintain a clean-working-tree invariant.
  • Validate compatibility with PRD_SCHEMA_EXTERNAL_AGENT_GUIDE and surface local version mismatches when detected.

Quick Start

Process all ready PRD specs in the configured queue and generate outcomes per PRD_SCHEMA.

Frequently Asked Questions about ls-agentic-prd-batch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PRD batch processing to update spec status and generate audit trails?

Automating PRD batch processing involves loading ready spec files, filtering by front matter status, prioritizing them, and updating their status to in-progress or done to generate auditable outcomes.

What is the best way to prioritize ready specs during PRD workflow automation?

Prioritizing ready specs during PRD workflow automation is done by sorting filtered spec files based on their priority attribute and then their date, ensuring higher-priority specifications are processed first.

How does spec management handle rollback instructions and verification steps for completed batches?

Spec management handles rollback and verification by writing outcome blocks that include the branch, commit SHA, changed files, verification steps, and rollback instructions to maintain a clean working tree invariant.

Can I exclude non-target files like README or INDEX when processing PRD spec queues?

Yes, you can exclude non-target files during PRD spec queue processing by filtering out README, INDEX, and SPEC-TEMPLATE files, ensuring only valid specifications are loaded and updated.

Why does PRD batch processing enforce version checks against the repository root?

PRD batch processing enforces version checks against the repository root to validate compatibility with the PRD schema and external agent guides, surfacing local version mismatches when detected to prevent workflow errors.

Do I need external confirmation rules to mark a PRD spec as done or blocked?

External confirmation rules are honored when specified by the PRD schema, meaning certain specs may require external approval before the workflow can mark their status as done or blocked upon completion.