prompt-builder
Build complete agent prompts deterministically via Python script. Use BEFORE spawning any BAZINGA agent (Developer, QA, Tech Lead, PM, etc.).
Security Assessment
About prompt-builder
The prompt-builder skill is designed to generate complete, deterministic prompts for BAZINGA agents through a structured Python script workflow. It addresses the challenge of consistently creating fully-formed agent prompts that integrate context, specialization, and agent-specific definitions without manual intervention. By automating this process, it ensures that agents like Developers, QA Experts, Tech Leads, PMs, and other roles receive prompts that are accurate, validated, and ready for immediate execution.
The skill's core capabilities include reading task specializations, context packages, reasoning patterns, and full agent definitions from both the database and the filesystem. It applies model-specific token budgets, validates required markers, and outputs both the prompt file and a JSON summary detailing success status, token usage, line count, and marker validation results. It also supports additional fields for retries, compact return protocols, and PM-specific spawns, making it versatile for different orchestrator needs.
This skill is primarily invoked right before spawning any BAZINGA agent, ensuring that agents operate with the most up-to-date context and parameters. Target users include orchestrators and developers within the BAZINGA ecosystem who need reliable prompt generation, as well as QA and PM teams who require validated prompts for testing and task handoffs. Its deterministic nature and integration with database and filesystem sources make it essential for automated agent orchestration in multi-role workflows.
FAQ
When should I use the prompt-builder skill?
You should invoke this skill immediately before spawning any BAZINGA agent to ensure the agent receives a complete and validated prompt.
What prerequisites are required to run this skill?
The database must be initialized, configuration must be seeded using the config-seeder skill, and agent definition files must exist in the agents/ directory.
How does the skill handle errors in prompt generation?
The skill outputs a JSON error response detailing missing markers and the error message. The orchestrator should verify the success field before proceeding to spawn the agent.
Can the skill handle retries or task handoffs?
Yes, additional fields in the parameters JSON allow handling QA feedback, TL feedback, prior handoff files, and PM state to support retries and context resumption.
Which agents can receive prompts generated by this skill?
It supports a variety of BAZINGA agents including Developers, QA Experts, Tech Leads, PMs, Investigators, and Requirements Engineers.
Install prompt-builder
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mehdic/bazinga