project-development

Evaluate task-model fit and design LLM project architectures for production pipelines.

Updated Apr 15, 2025
One-click install
npx skills add https://github.com/khrore/nix-config --skill project-development-khrore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-development
Source: https://github.com/khrore/nix-config/tree/main/dotfiles/common/.config/opencode/skills/project-development
Command: npx skills add https://github.com/khrore/nix-config --skill project-development-khrore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Projects that intend to use LLMs often fail because teams misunderstand task-model fit, bake in non-idempotent architectures, or underestimate token costs and parsing fragility; this Skill helps teams evaluate, plan, and structure LLM-powered projects to avoid those mistakes and iterate rapidly.

Core Features & Use Cases

  • Task-Model Fit Evaluation: Practical checklists and a manual-prototype step to decide whether to use LLMs, traditional code, or agents.
  • Staged Pipeline Patterns: Canonical acquire → prepare → process → parse → render architecture with guidance on idempotency, caching, and file-system state as the source of truth.
  • Agent & Multi-Agent Guidance: When to use single-agent vs multi-agent designs, architectural reduction patterns, and sub-agent isolation strategies.
  • Parsing, Validation & Costing: Prompt formats for structured output, robust parsing strategies with graceful degradation, and simple token-cost estimation formulas for batch workloads.
  • Use Cases: Batch content analysis, text-to-structured-data pipelines, interactive agent applications, and research orchestration with parallel sub-agents.

Quick Start

Run a manual prototype: copy one representative input into the model, verify output format and quality, then scaffold an acquire/prepare/process/parse/render directory for that item.

Frequently Asked Questions about project-development

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

FAQPage Schema
How do I design an LLM pipeline architecture for production batch processing?

Design LLM pipelines using a staged acquire, prepare, process, parse, and render architecture. This pattern manages file-system state as the source of truth, enabling idempotency and caching to ensure robust batch processing workflows.

How do I estimate token costs for LLM batch processing workloads?

Calculate expected expenses by applying simple token-cost estimation formulas to your LLM batch processing workloads. These formulas evaluate workload volume against model token pricing to project pipeline costs before scaling.

When should I use multi-agent systems versus a single LLM for project tasks?

Use multi-agent systems for complex research orchestration and single agents for isolated development tasks. Evaluate task-model fit using practical checklists and a manual-prototype step to decide between LLMs, traditional code, or agents before committing.

Why does my LLM structured output parsing fail and how do I fix it?

LLM structured output parsing fails due to format inconsistencies, but you can fix it using robust parsing strategies with graceful degradation. Apply structured-output prompting formats to enforce reliable extraction and prevent pipeline failures during processing.

What is the best way to manage state in an LLM agent pipeline?

Manage state in an LLM agent pipeline by using the file system as the source of truth. This architecture ensures idempotency and enables caching across staged pipeline patterns, preventing data loss during multi-agent research orchestration workflows.