playbook-architect

Name: playbook-architect
Author: DNYoussef

32stars6forks

How to install playbook-architect?

dnyoussef/context-cascade/playbook-architect

$npx -y skills add DNYoussef/context-cascade --skill playbook-architect

Installs into the current project.

Summary

/*============================================================================*/ /* PLAYBOOK-ARCHITECT SKILL :: VERILINGUA x VERIX EDITION */ /*============================================================================*/

Files · 1

View on GitHub

SKILL.md

1	/============================================================================/
2	/* PLAYBOOK-ARCHITECT SKILL :: VERILINGUA x VERIX EDITION */
3	/============================================================================/
4
5	---
6	name: playbook-architect
7	version: 1.0.0
8	description: \|
9	[assert\|neutral] Comprehensive framework for creating, analyzing, and optimizing playbooks that orchestrate skill sequences. Use when creating new playbooks, improving existing playbook workflows, or applying evidence [ground:given] [conf:0.95] [state:confirmed]
10	category: foundry
11	tags:
12	- foundry
13	- creation
14	- meta-tools
15	- orchestration
16	author: ruv
17	cognitive_frame:
18	primary: evidential
19	goal_analysis:
20	first_order: "Execute playbook-architect workflow"
21	second_order: "Ensure quality and consistency"
22	third_order: "Enable systematic foundry processes"
23	---
24
25	/----------------------------------------------------------------------------/
26	/* S0 META-IDENTITY */
27	/----------------------------------------------------------------------------/
28
29	[define\|neutral] SKILL := {
30	name: "playbook-architect",
31	category: "foundry",
32	version: "1.0.0",
33	layer: L1
34	} [ground:given] [conf:1.0] [state:confirmed]
35
36	/----------------------------------------------------------------------------/
37	/* S1 COGNITIVE FRAME */
38	/----------------------------------------------------------------------------/
39
40	[define\|neutral] COGNITIVE_FRAME := {
41	frame: "Evidential",
42	source: "Turkish",
43	force: "How do you know?"
44	} [ground:cognitive-science] [conf:0.92] [state:confirmed]
45
46	## Kanitsal Cerceve (Evidential Frame Activation)
47	Kaynak dogrulama modu etkin.
48
49	/----------------------------------------------------------------------------/
50	/* S2 TRIGGER CONDITIONS */
51	/----------------------------------------------------------------------------/
52
53	[define\|neutral] TRIGGER_POSITIVE := {
54	keywords: ["playbook-architect", "foundry", "workflow"],
55	context: "user needs playbook-architect capability"
56	} [ground:given] [conf:1.0] [state:confirmed]
57
58	/----------------------------------------------------------------------------/
59	/* S3 CORE CONTENT */
60	/----------------------------------------------------------------------------/
61
62	<!-- SKILL SOP IMPROVEMENT v1.0 -->
63	## Skill Execution Criteria
64
65	### When to Use This Skill
66	- Creating new playbooks for recurring workflow patterns
67	- Improving existing playbooks with inconsistent or suboptimal routing
68	- Building playbook libraries for team standardization
69	- Optimizing high-stakes workflows where execution order impacts outcomes
70	- Debugging why playbooks aren't producing expected results
71	- Adding new categories of playbooks (gap analysis)
72	- Consolidating overlapping playbooks
73
74	### When NOT to Use This Skill
75	- For single-skill invocations (use skill directly)
76	- When existing playbook already covers the workflow optimally
77	- For one-off tasks without reuse value
78	- When task is purely conversational without orchestration needs
79
80	### Success Criteria
81	- [assert\|neutral] primary_outcome: "Optimized playbook with clear trigger conditions, correct skill sequencing, proper dependency handling, and maximized parallelization" [ground:acceptance-criteria] [conf:0.90] [state:provisional]
82	- [assert\|neutral] quality_threshold: 0.92 [ground:acceptance-criteria] [conf:0.90] [state:provisional]
83	- [assert\|neutral] verification_method: "Playbook executes successfully across diverse test cases, routes correctly based on intent keywords, and achieves stated success metrics" [ground:acceptance-criteria] [conf:0.90] [state:provisional]
84
85	### Edge Cases
86	- case: "Overlapping trigger keywords with existing playbooks"
87	handling: "Apply MECE analysis to disambiguate, add priority weights or more specific keywords"
88	- case: "Circular dependencies between skills in sequence"
89	handling: "Detect cycles, restructure into DAG (Directed Acyclic Graph), split if necessary"
90	- case: "Missing MCP requirements for skill execution"
91	handling: "Add mcp_requirements section, validate MCPs are available before routing"
92
93	### Skill Guardrails
94	NEVER:
95	- "Create playbooks without validating skill availability (skills must exist in registry)"
96	- "Sequence skills with unmet dependencies (prerequisites must complete before dependents)"
97	- "Skip parallelization analysis (concurrent execution is 2-8x faster)"
98	- "Duplicate existing playbooks without clear differentiation"
99	- "Create playbooks with vague trigger conditions (keywords must be specific)"
100	ALWAYS:
101	- "Validate all skills in sequence exist in skills/ directory"
102	- "Apply dependency analysis to identify sequential vs parallel phases"
103	- "Include success criteria with measurable metrics"
104	- "Document MCP requirements for each playbook"
105	- "Add fallback skill

People who liked this also viewed

6 picks

Type

playbook-architect

32stars6forks

View on GitHub

How to install playbook-architect?

dnyoussef/context-cascade/playbook-architect

$npx -y skills add DNYoussef/context-cascade --skill playbook-architect

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	/============================================================================/
2	/* PLAYBOOK-ARCHITECT SKILL :: VERILINGUA x VERIX EDITION */
3	/============================================================================/
4
5	---
6	name: playbook-architect
7	version: 1.0.0
8	description: \|
9	[assert\|neutral] Comprehensive framework for creating, analyzing, and optimizing playbooks that orchestrate skill sequences. Use when creating new playbooks, improving existing playbook workflows, or applying evidence [ground:given] [conf:0.95] [state:confirmed]
10	category: foundry
11	tags:
12	- foundry
13	- creation
14	- meta-tools
15	- orchestration
16	author: ruv
17	cognitive_frame:
18	primary: evidential
19	goal_analysis:
20	first_order: "Execute playbook-architect workflow"
21	second_order: "Ensure quality and consistency"
22	third_order: "Enable systematic foundry processes"
23	---
24
25	/----------------------------------------------------------------------------/
26	/* S0 META-IDENTITY */
27	/----------------------------------------------------------------------------/
28
29	[define\|neutral] SKILL := {
30	name: "playbook-architect",
31	category: "foundry",
32	version: "1.0.0",
33	layer: L1
34	} [ground:given] [conf:1.0] [state:confirmed]
35
36	/----------------------------------------------------------------------------/
37	/* S1 COGNITIVE FRAME */
38	/----------------------------------------------------------------------------/
39
40	[define\|neutral] COGNITIVE_FRAME := {
41	frame: "Evidential",
42	source: "Turkish",
43	force: "How do you know?"
44	} [ground:cognitive-science] [conf:0.92] [state:confirmed]
45
46	## Kanitsal Cerceve (Evidential Frame Activation)
47	Kaynak dogrulama modu etkin.
48
49	/----------------------------------------------------------------------------/
50	/* S2 TRIGGER CONDITIONS */
51	/----------------------------------------------------------------------------/
52
53	[define\|neutral] TRIGGER_POSITIVE := {
54	keywords: ["playbook-architect", "foundry", "workflow"],
55	context: "user needs playbook-architect capability"
56	} [ground:given] [conf:1.0] [state:confirmed]
57
58	/----------------------------------------------------------------------------/
59	/* S3 CORE CONTENT */
60	/----------------------------------------------------------------------------/
61
62	<!-- SKILL SOP IMPROVEMENT v1.0 -->
63	## Skill Execution Criteria
64
65	### When to Use This Skill
66	- Creating new playbooks for recurring workflow patterns
67	- Improving existing playbooks with inconsistent or suboptimal routing
68	- Building playbook libraries for team standardization
69	- Optimizing high-stakes workflows where execution order impacts outcomes
70	- Debugging why playbooks aren't producing expected results
71	- Adding new categories of playbooks (gap analysis)
72	- Consolidating overlapping playbooks
73
74	### When NOT to Use This Skill
75	- For single-skill invocations (use skill directly)
76	- When existing playbook already covers the workflow optimally
77	- For one-off tasks without reuse value
78	- When task is purely conversational without orchestration needs
79
80	### Success Criteria
81	- [assert\|neutral] primary_outcome: "Optimized playbook with clear trigger conditions, correct skill sequencing, proper dependency handling, and maximized parallelization" [ground:acceptance-criteria] [conf:0.90] [state:provisional]
82	- [assert\|neutral] quality_threshold: 0.92 [ground:acceptance-criteria] [conf:0.90] [state:provisional]
83	- [assert\|neutral] verification_method: "Playbook executes successfully across diverse test cases, routes correctly based on intent keywords, and achieves stated success metrics" [ground:acceptance-criteria] [conf:0.90] [state:provisional]
84
85	### Edge Cases
86	- case: "Overlapping trigger keywords with existing playbooks"
87	handling: "Apply MECE analysis to disambiguate, add priority weights or more specific keywords"
88	- case: "Circular dependencies between skills in sequence"
89	handling: "Detect cycles, restructure into DAG (Directed Acyclic Graph), split if necessary"
90	- case: "Missing MCP requirements for skill execution"
91	handling: "Add mcp_requirements section, validate MCPs are available before routing"
92
93	### Skill Guardrails
94	NEVER:
95	- "Create playbooks without validating skill availability (skills must exist in registry)"
96	- "Sequence skills with unmet dependencies (prerequisites must complete before dependents)"
97	- "Skip parallelization analysis (concurrent execution is 2-8x faster)"
98	- "Duplicate existing playbooks without clear differentiation"
99	- "Create playbooks with vague trigger conditions (keywords must be specific)"
100	ALWAYS:
101	- "Validate all skills in sequence exist in skills/ directory"
102	- "Apply dependency analysis to identify sequential vs parallel phases"
103	- "Include success criteria with measurable metrics"
104	- "Document MCP requirements for each playbook"
105	- "Add fallback skill

People who liked this also viewed

6 picks

Type