parallel-prompt-generator

Generate agent-ready prompts from existing task specification files. Use when regenerating prompts after editing tasks, updating prompt templates, or preparing tasks for cpo execution.

跳到安装

仓库: ForceInjection/domain-driven-design-skills
最近来源活动: 2026年5月8日 03:07
检测到的 SKILL.md 语言: 英语
星标: 25
分支: 7

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/ForceInjection/domain-driven-design-skills --skill parallel-prompt-generator

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

2 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

academic-research

Conduct deep academic research for philosophy, neuroscience, cognitive science, and theoretical computer science (computability, complexity, AI theory, logic). Use when user asks to: research academic topics, find scholarly papers, conduct literature reviews, analyze citations, synthesize research findings, explore philosophical arguments, investigate consciousness/cognition, study computability/decidability/Turing machines, or analyze academic debates. Triggers on: 'research papers', 'literature review', 'academic sources', 'scholarly articles', 'philosophy of mind', 'computability theory', 'neuroscience studies', 'find papers on', 'what does the research say'.

2026-05-08

action-plan-150

Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.

2026-05-08

add-keyboard-nav

Add keyboard navigation to a feature using CommandRegistryService. Use when implementing keyboard shortcuts, vim-style navigation, or hotkeys for a page or component.

2026-05-08

查看这个仓库的全部 Skills

parallel/TS-XXXX-slug/
  manifest.json       # Required: wave structure, agents
  context.md          # Required: shared context
  contracts/          # Required: types.py, api-schema.yaml
  tasks/              # Required: task-*.md files
    task-001-users.md
    task-002-products.md

parallel/TS-XXXX-slug/
  prompts/
    agent-prompts.md   # Wave summary and launch commands
    task-001.txt       # Individual agent prompt
    task-002.txt
    ...

flowchart TB
    Start[("tasks/ folder")]
    Read["1. Read manifest.json"]
    Context["2. Load context.md"]
    Parse["3. Parse each task file"]
    Generate["4. Generate task-NNN.txt"]
    Summary["5. Create agent-prompts.md"]
    Done[("prompts/ ready")]

    Start --> Read
    Read --> Context
    Context --> Parse
    Parse --> Generate
    Generate --> Summary
    Summary --> Done

Extract YAML frontmatter:

id: task-001
component: users
wave: 1
deps: []
agent: python-experts:django-expert
contracts: [contracts/types.py, contracts/api-schema.yaml]

Extract Markdown sections:
- ## Scope -> CREATE, MODIFY, BOUNDARY
- ## Requirements -> Implementation requirements
- ## Checklist -> Acceptance criteria
Resolve skills for each task:
- Read parallel-agents/agent-skills-mapping.yaml for agent-to-skills mapping
- Look up the agent from task frontmatter (e.g., python-experts:django-expert)
- Get the skills list for that agent
- Format as full skill names: plugin:skill-name

TASK-{id}: {title}
Agent: {agent}
Wave: {wave}
Dependencies: {deps or "None"}

=== REQUIRED SKILLS ===
Before starting implementation, invoke these skills to load best practices:
{list of skills from agent-skills-mapping.yaml, formatted as bullets}

Invoke skills using: skill: "plugin:skill-name"

=== CONTEXT ===
{contents of context.md}

=== OBJECTIVE ===
{First line of task description or component name}

=== CONTRACTS ===
Reference these contract files before implementing:
{list of contract files with full paths}

=== FILES TO CREATE ===
{CREATE section from Scope}

=== FILES TO MODIFY ===
{MODIFY section from Scope}

=== DO NOT MODIFY ===
{BOUNDARY section from Scope}

=== IMPLEMENTATION REQUIREMENTS ===
{Requirements section content}

=== ACCEPTANCE CRITERIA ===
{Checklist section content}

=== EXECUTION INSTRUCTIONS ===

You MUST write code, not just describe it. Follow these steps:

1. **Read contracts first**: Read all files in contracts/ to understand interfaces
2. **Read existing code**: If modifying files, read them first
3. **Implement**: Use Write/Edit tools to create/modify code
4. **Test & Fix Loop**:
   - Run tests for your implementation
   - If ANY test fails, FIX the issue and rerun tests
   - REPEAT until ALL tests pass
   - Do NOT proceed to step 5 until tests pass
5. **Lint**: Run linters (ruff, mypy, eslint as appropriate)
6. **Commit**: Create atomic commit with conventional format (only after tests pass)

=== IMPORTANT RULES ===

- Do NOT ask for confirmation - proceed immediately with implementation
- Do NOT modify files listed in DO NOT MODIFY section
- Do NOT skip writing tests
- Do NOT deviate from contract interfaces
- Do NOT commit or signal completion until ALL tests pass
- If tests fail, you MUST fix the issues and keep running until they pass
- STOP if you encounter blocking issues and report in output

**CRITICAL - CONTRACTS ARE DESIGN DOCUMENTS:**
- Contracts in `parallel/` are DESIGN SPECIFICATIONS ONLY
- READ them to understand the interface you must implement
- RECREATE the types/interfaces in your actual project code
- NEVER import from `parallel/` directory
- NEVER use sys.path manipulation to access parallel/ files
- The `parallel/` directory is NOT part of the deployed codebase

=== COMPLETION SIGNAL ===

Upon successful completion (ALL tests passing), run: touch .claude-task-complete

CRITICAL: Only signal completion if:
- All tests pass (pytest exits with 0)
- All linting passes
- Code is committed

# Agent Prompts for {name}

Generated: {timestamp}
Tech Spec: {tech_spec_id}
Total Tasks: {count}

## Wave Execution Order

### Wave 1 (Parallel)
| Task | Agent | Component |
|------|-------|-----------|
| task-001 | python-experts:django-expert | users |
| task-002 | python-experts:django-expert | products |

### Wave 2 (Parallel, depends on Wave 1)
| Task | Agent | Component |
|------|-------|-----------|
| task-003 | python-experts:django-expert | orders |

## Launch Commands

### Using cpo (Recommended)
```bash
cpo run parallel/{slug}/

# Run in parallel terminals or with &
claude --prompt-file prompts/task-001.txt --agent python-experts:django-expert &
claude --prompt-file prompts/task-002.txt --agent python-experts:django-expert &
wait

# After Wave 1 completes
claude --prompt-file prompts/task-003.txt --agent python-experts:django-expert


## Validation Before Generation

Check these conditions:

- [ ] `manifest.json` exists and is valid JSON
- [ ] `context.md` exists
- [ ] `contracts/` directory exists with at least one file
- [ ] `tasks/` directory has at least one task file
- [ ] All tasks referenced in manifest exist in `tasks/`

## Error Handling

### Task Not in Manifest


### Missing Contract Reference


## Regeneration Mode

When prompts already exist:

1. **Backup existing**: Move to `prompts.backup-{timestamp}/`
2. **Generate fresh**: Create new prompts from current tasks
3. **Report diff**: Show what changed

```bash
# Command triggers regeneration
/parallel-generate-prompts parallel/TS-0042-inventory/ --force

# Quick validation - each prompt should have these markers
for f in prompts/task-*.txt; do
  echo "=== $f ==="
  grep -c "=== REQUIRED SKILLS ===" "$f" || echo "MISSING: REQUIRED SKILLS"
  grep -c "=== EXECUTION INSTRUCTIONS" "$f" || echo "MISSING: EXECUTION INSTRUCTIONS"
  grep -c "=== COMPLETION SIGNAL" "$f" || echo "MISSING: COMPLETION SIGNAL"
done

Skill	Relationship
`parallel-decompose`	Creates tasks/ that this skill reads
`parallel-task-format`	Defines the task YAML format parsed here
`parallel-execution`	Consumes the prompts/ this skill generates
`parallel-agents`	Overall workflow context + agent-skills-mapping.yaml

Section	Purpose	Required
`=== REQUIRED SKILLS ===`	Skills to invoke at start	YES
`=== CONTEXT ===`	Shared project context	YES
`=== OBJECTIVE ===`	Task goal	YES
`=== CONTRACTS ===`	Contract file references	YES
`=== FILES TO CREATE ===`	Scope CREATE

Section	Purpose	Required
`=== REQUIRED SKILLS ===`	Skills to invoke at start	YES
`=== CONTEXT ===`	Shared project context	YES
`=== OBJECTIVE ===`	Task goal	YES
`=== CONTRACTS ===`	Contract file references	YES
`=== FILES TO CREATE ===`	Scope CREATE

parallel-prompt-generator

安装方式

检查来源文件

Prompt Generator

CRITICAL: Prompt Template Requirements

Prompt Generator

CRITICAL: Prompt Template Requirements

When to Use

Input Requirements

Output

Workflow

Step 1: Read manifest.json

Step 2: Load context.md

Step 3: Parse Task Files

Step 4: Generate Individual Prompts

Step 5: Create agent-prompts.md

Manual Execution (Wave 1)

Manual Execution (Wave 2)

Prompt Files

Token Optimization

Integration with cpo

Post-Generation Validation

Related Skills

Reference Files

name	parallel-prompt-generator
short	Generate agent prompts from task specs
description	Generate agent-ready prompts from existing task specification files. Use when regenerating prompts after editing tasks, updating prompt templates, or preparing tasks for cpo execution.
when	User wants to generate prompts from tasks, regenerate prompts after task edits, create agent-ready instructions from task specs, or refresh the prompts/ folder

File	Task	Lines
prompts/task-001.txt	task-001-users	~150
prompts/task-002.txt	task-002-products	~145
prompts/task-003.txt	task-003-orders	~160

parallel-prompt-generator

来源信息

安装方式

检查来源文件

同仓库更多 Skills

Prompt Generator

CRITICAL: Prompt Template Requirements

同仓库更多 Skills

Prompt Generator

CRITICAL: Prompt Template Requirements

When to Use

Input Requirements

Output

Workflow

Step 1: Read manifest.json

Step 2: Load context.md

Step 3: Parse Task Files

Step 4: Generate Individual Prompts

Step 5: Create agent-prompts.md

Manual Execution (Wave 1)

Manual Execution (Wave 2)

Prompt Files

Token Optimization

Integration with cpo

Post-Generation Validation

Related Skills

Reference Files