Prd V03 Features Value Planning
mattgierhart/PRD-driven-context-engineering
Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model.
Specialized business logic evaluator for the Evaluate-Loop. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Install Eval Business Logic
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor eval-business-logic --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/eval-business-logic .claude/skills/eval-business-logic && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "eval-business-logic" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logic into .claude/skills/eval-business-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eval-business-logic", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logicType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor eval-business-logic --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/eval-business-logic .agents/skills/eval-business-logic && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eval-business-logic" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logic into .agents/skills/eval-business-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eval-business-logic", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor eval-business-logic --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/eval-business-logic .cursor/skills/eval-business-logic && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "eval-business-logic" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logic into .cursor/skills/eval-business-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eval-business-logic", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/eval-business-logic--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor eval-business-logic --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/eval-business-logic .gemini/skills/eval-business-logic && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "eval-business-logic" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logic into .gemini/skills/eval-business-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eval-business-logic", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor eval-business-logicInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/eval-business-logic .github/skills/eval-business-logic && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "eval-business-logic" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logic into .github/skills/eval-business-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eval-business-logic", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor eval-business-logic --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/eval-business-logic .opencode/skills/eval-business-logic && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "eval-business-logic" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/eval-business-logic into .opencode/skills/eval-business-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eval-business-logic", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
eval-business-logic- GitHub stars
- 381
- Token cost
- ~1.6k tokens
- SKILL.md length
- 439 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Specialized business logic evaluator for the Evaluate-Loop. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
- Works in 5 steps: Track's spec.md and plan.md → conductor/product.md — product rules… → Project-specific pipeline/prompt… → …
- Tasks that involve Customer journey mapping
- SKILL.md covers When This Evaluator Is Used, Inputs Required, Evaluation Passes (6 checks) and Verdict Template, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Eval Business Logic is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product logic — pipelines, dependency resolution, state machines, pricing/tier enforcement, packaging. Checks feature correctness against product rules, edge cases, state transitions, data flow, and user journey completeness. Dispatched by loop-execution-evaluator when track type is 'business-logic', 'generator', or 'core-feature'. Triggered by: 'evaluate logic', 'test business rules', 'verify business…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Customer journey mapping and Pricing strategy. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Customer journey mapping
- Tasks that involve Pricing strategy
Example prompts
- “business-logic”
- “generator”
- “core-feature”
- “/eval-business-logic”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Track's spec.md and plan.md
- conductor/product.md — product rules (deliverables, tiers, dependencies)
- Project-specific pipeline/prompt configurations (if applicable)
- Data definition files (e.g., asset definitions, feature configs)
- Implementation code being evaluated
What it can do on your machine
Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Eval Business Logic loads about 1.6k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 439 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 439 words, ~1,554 tokens.
Download SKILL.mdSave it as
.claude/skills/eval-business-logic/SKILL.md (or your agent's skills folder).- name
- eval-business-logic
- description
- Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product logic — pipelines, dependency resolution, state machines, pricing/tier enforcement, packaging. Checks feature correctness against product rules, edge cases, state transitions, data flow, and user journey completeness. Dispatched by loop-execution-evaluator when track type is 'business-logic', 'generator', or 'core-feature'. Triggered by: 'evaluate logic', 'test business rules', 'verify business rules', 'check feature'.
Business Logic Evaluator Agent
Specialized evaluator for tracks that implement core product logic — generation pipelines, state machines, pricing, or other business-rule-heavy features.
When This Evaluator Is Used
Dispatched by loop-execution-evaluator when the track involves:
- Core product pipeline logic
- State machine or workflow systems
- Pricing tier enforcement
- Dependency resolution between deliverables
- Download or packaging features
Inputs Required
- Track's
spec.mdandplan.md conductor/product.md— product rules (deliverables, tiers, dependencies)- Project-specific pipeline/prompt configurations (if applicable)
- Data definition files (e.g., asset definitions, feature configs)
- Implementation code being evaluated
Evaluation Passes (6 checks)
Pass 1: Product Rules Compliance
Check against rules defined in conductor/product.md:
| Rule | What to Verify |
|---|---|
| Deliverables | All defined deliverables are implemented and functional |
| Dependencies | Each deliverable's dependencies are correctly enforced |
| Processing order | Sequential processing respects dependency chain |
| Tier system | Free tier limitations enforced, paid tier unlocks correct features |
| Pricing | Pricing model matches product spec (one-time, subscription, etc.) |
| State rules | State transitions (e.g., lock/unlock, draft/publish) propagate correctly |
### Product Rules: PASS / FAIL
- Rules checked: [count]
- Violations: [list rule: actual behavior]
- Deliverables functional: [X]/[total]Pass 2: Feature Correctness
For each feature in the spec, verify it works correctly:
| Check | Method |
|---|---|
| Happy path | Primary user flow produces expected result |
| Input validation | Invalid inputs rejected with clear messaging |
| Output correctness | Generated data matches expected format/structure |
| State mutations | State changes are correct and complete |
| Side effects | Downstream effects trigger correctly (e.g., dependency propagation) |
### Feature Correctness: PASS / FAIL
- Features tested: [count]
- Correct: [count]
- Failures: [describe each]Pass 3: Edge Cases
| Scenario | What to Verify |
|---|---|
| Empty state | First-time user with no data |
| Boundary values | Max input length, empty inputs, special characters |
| Concurrent operations | What happens if user triggers 2 operations at once |
| Network failure mid-operation | Partial state handled correctly |
| Re-processing | Re-running an operation on existing data prompts confirmation if needed |
| All items locked/finalized | UI reflects that no further changes are possible |
| Tier limits | Exceeding free tier limit shows upgrade prompt |
### Edge Cases: PASS / FAIL
- Scenarios checked: [count]
- Unhandled: [list]
- User impact: [describe]Show full SKILL.md (152 more words)Show less
Pass 4: State Transitions
Verify state machine correctness for your project's state model. Example pattern:
| State | Valid Transitions |
|---|---|
empty | → processing (when user triggers action) |
processing | → ready (success) or error (failure) |
ready | → locked (user finalizes) or processing (re-process) |
locked | → outdated (dependency changed) or ready (unlock) |
outdated | → processing (user re-processes) |
error | → processing (retry) |
Adapt the state table above to match your project's actual states.
### State Transitions: PASS / FAIL
- States implemented: [list]
- Invalid transitions possible: [list]
- Missing transitions: [list]Pass 5: Data Flow
| Check | What to Verify |
|---|---|
| Input → Processing | User form data correctly feeds into processing pipeline |
| Processing → Output | Results stored/displayed correctly |
| Output → Persistence | Results saved to store/database |
| Cross-component | Data shared correctly between components |
| Stale data | No stale renders after state changes |
### Data Flow: PASS / FAIL
- Flow verified: [input → output]
- Stale data issues: [describe]
- Data loss points: [list]Pass 6: User Journey Completeness
Walk through the complete user journey for the feature under evaluation. Example structure:
1. User provides input (form, selection, etc.)
2. System processes input
3. User reviews output
4. User can lock/finalize results
5. System handles dependencies between outputs
6. User views all deliverables
7. User can export/download results
8. User can re-process any unlocked item
9. Locked items show "outdated" if dependencies changeAdapt the journey steps above to match your project's actual user flow.
### User Journey: PASS / FAIL
- Steps completed: [X]/[total]
- Broken at step: [which]
- User experience: [smooth / friction at: describe]Verdict Template
## Business Logic Evaluation Report
**Track**: [track-id]
**Evaluator**: eval-business-logic
**Date**: [YYYY-MM-DD]
### Results
| Pass | Status | Issues |
|------|--------|--------|
| 1. Product Rules | PASS/FAIL | [details] |
| 2. Feature Correctness | PASS/FAIL | [details] |
| 3. Edge Cases | PASS/FAIL | [details] |
| 4. State Transitions | PASS/FAIL | [details] |
| 5. Data Flow | PASS/FAIL | [details] |
| 6. User Journey | PASS/FAIL | [details] |
### Verdict: PASS / FAIL
[If FAIL, list specific fix actions for loop-fixer]Handoff
- PASS → Return to
loop-execution-evaluator→ Conductor marks complete - FAIL → Return to
loop-execution-evaluator→ Conductor dispatchesloop-fixer
© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/eval-business-logic of Ibrahim-3d/orchestrator-supaconductor.
Open the folder on GitHubat commit 76c9b10
Compare with similar skills
Eval Business Logic next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Eval Business Logic this skillIbrahim-3d/orchestrator-supaconductor | 381 | — | ~1.6k | Automated safety check: Pass | AGPL-3.0 | |
| Prd V03 Features Value Planningmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Monetizing Innovationwondelai/skills | 2.4k | — | ~5.2k | Automated safety check: Pass | MIT | |
| Prd V03 Pricing Modelmattgierhart/PRD-driven-context-engineering | 180 | — | ~3k | Automated safety check: Pass | MIT | |
| Continuous Discoverywondelai/skills | 2.4k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Grad Platform Economicsasgard-ai-platform/skills | 242 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Monetizing Innovation
wondelai/skills
Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".
Prd V03 Pricing Model
mattgierhart/PRD-driven-context-engineering
Select and validate pricing model for PRD v0.3 Commercial Model.
Continuous Discovery
wondelai/skills
Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots.
Grad Platform Economics
asgard-ai-platform/skills
Apply platform economics to analyze network effects, solve chicken-and-egg problems, and design multi-sided platform pricing strategies.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
More from Ibrahim-3d/orchestrator-supaconductor
All 27 skills in this repoCto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
Agent Factory
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
Board Of Directors
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
Business Docs Sync
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Context Loader
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Related
Questions about Eval Business Logic
What does Eval Business Logic do?
Specialized business logic evaluator for the Evaluate-Loop. An agent skill from Ibrahim-3d/orchestrator-supaconductor. Eval Business Logic is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Specialized business logic evaluator for the Evaluate-Loop.
When should I use Eval Business Logic?
Eval Business Logic fits situations like: tasks that involve Customer journey mapping; tasks that involve Pricing strategy.
How do I install Eval Business Logic in Claude Code?
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a claude-code`. Or copy the skill folder (skills/eval-business-logic in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/eval-business-logic in your project. Claude Code loads it when a task matches its description.
How do I install Eval Business Logic in Codex?
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a codex`. Or copy the skill folder (skills/eval-business-logic in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/eval-business-logic in your project. Codex loads it when a task matches its description.
Can I use Eval Business Logic in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill eval-business-logic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eval-business-logic, .gemini/skills/eval-business-logic, .github/skills/eval-business-logic and .opencode/skills/eval-business-logic in your project.
What does Eval Business Logic need to run?
SKILL.md names no scripts, command-line tools or credentials: Eval Business Logic is instructions for the agent only.
Does Eval Business Logic access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Eval Business Logic safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Eval Business Logic use?
Eval Business Logic is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Eval Business Logic use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Eval Business Logic?
Skills that share tags, products or a category with Eval Business Logic: Prd V03 Features Value Planning (mattgierhart/PRD-driven-context-engineering, 180 stars), Monetizing Innovation (wondelai/skills, 2.4k stars), Prd V03 Pricing Model (mattgierhart/PRD-driven-context-engineering, 180 stars) and Continuous Discovery (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eval Business Logic?
Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 381 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.
Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.