designing-logic-models
Guides users interactively to design, review, and document program logic models, results chains, outcome chains, theories of change, and results frameworks. Use when mapping causal relationships from inputs and activities to outputs and successive outcomes for a project or objective, validating causal assumptions, or generating BC Gov-styled Mermaid diagrams and logframe matrices. Not for drafting the strategic vision, objectives, measures or roadmap (use developing-and-managing-strategy), logging items (use triaging-new-items), team capacity (use managing-team-skills-and-allocation) or presentation decks (use rendering-strategic-visuals-and-decks).
Target: Presentations. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Designing logic models
- Contents
- Constraints
- Quick start
- Workflow
- Related skills
- Verification
- References
Guides teams through an interactive conversation to construct, stress-test, and document robust causal results chains—from resources and activities through controllable outputs to progressive immediate, intermediate, and long-term public outcomes. Constraints Quick start Workflow Verification References 1. Strict causal purity: Rigorously separate activities (work done), outputs (things produced), and outcomes (behavioral or operational changes resulting from use). 2. Intermediate stepping: Reject unmediated leaps from early outputs to macro impacts without immediate and intermediate stepping stones. 3. Attribution vs. contribution: Direct control applies only to outputs; long-term outcomes must be framed as contribution alongside external influences. 4. Guided interaction: Guide the user step by step with questions, following guided-interaction.md: open with a numbered menu or one question, ask 1–2 per turn with a recommended default, show progress, accept "I don't know" as an open item, and confirm a recap before every write. 5. B.C. Government style: Use sentence case, plain language, zero emoji, zero exclamation marks, and official BC Gov token hex colors in Mermaid diagrams. 1
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- bcgov/strategic-planning-workbench
- Source file
- plugins/strategic-planning/.apm/skills/designing-logic-models/SKILL.md
- Fixed revision
- a9dc2f93b6a38b5115ec6cdbb18601dd39e4a37b
Requirements
- Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.
A small first task
先阅读原作者说明,再决定是否在自己的 AI 工具中使用。
Instructions for your AI tool
- Claude Desktop: resource-specific guide not available yet
- Claude Code: resource-specific guide not available yet
- Cursor: resource-specific guide not available yet
- Codex: resource-specific guide not available yet
Author documentation is not live verification by this site. Without evidence, we do not mark a resource as compatible, safe or free.
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: bcgov/strategic-planning-workbench · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-12T09:01:46.308Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.