Strategy FrameworkSAFE
Overview
An agent skill published by revfactory.
459e1bb8f76eOBSERVED · 2026-10-12What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: strategy-framework
description: "A full pipeline that systematizes an organization's strategy framework through OKR design, BSC mapping, SWOT analysis, vision & mission statement, and strategy execution roadmap. Use this skill for 'build a strategy framework,' 'design OKRs,' 'BSC analysis,' 'SWOT analysis,' 'write vision and mission,' 'strategy roadmap,' 'strategy formulation,' 'mid-to-long-term strategy,' 'business strategy framework,' and 'strategy system design' — across the full spectrum of organizational strategy development. It also supports supplementing and validating existing OKRs or SWOT analyses. Note: Financial statement preparation, ERP system implementation, performance review execution, and real-time KPI dashboard development are outside the scope of this skill."
---
# Strategy Framework — Full Strategy Pipeline
Systematizes an organization's strategy through the sequence: OKR → BSC → SWOT → Vision & Mission → Execution Roadmap.
## Execution Mode
**Agent Team** — 5 agents communicate directly via SendMessage and cross-verify each other's work.
## Agent Composition
| Agent | File | Role | Type |
|-------|------|------|------|
| okr-designer | `.claude/agents/okr-designer.md` | OKR goal & key result design, alignment | general-purpose |
| bsc-analyst | `.claude/agents/bsc-analyst.md` | BSC four-perspective mapping, KPI system | general-purpose |
| swot-specialist | `.claude/agents/swot-specialist.md` | SWOT analysis, TOWS strategy derivation | general-purpose |
| strategy-writer | `.claude/agents/strategy-writer.md` | Vision & mission, strategy execution roadmap | general-purpose |
| strategy-reviewer | `.claude/agents/strategy-reviewer.md` | Cross-verification, consistency checking | general-purpose |
## Workflow
### Phase 1: Preparation (Performed directly by the orchestrator)
1. Extract from user input:
- **Organization Info**: Name, industry, size, current situation
- **Strategy Period**: Annual/3-year/5-year
- **Existing Strategy Assets** (optional): Existing OKRs, vision & mission, analytical materials
- **Special Requirements** (optional): Emphasis on specific frameworks, focus on certain perspectives
2. Create the `_workspace/` directory at the project root
3. Organize input and save as `_workspace/00_input.md`
4. If existing files are present, copy them to `_workspace/` and skip the corresponding phase
5. **Determine the execution mode** based on request scope
### Phase 2: Team Assembly and Execution
| Order | Task | Owner | Dependencies | Deliverable |
|-------|------|-------|-------------|-------------|
| 1 | OKR design | okr-designer | None | `_workspace/01_okr_design.md` |
| 2a | BSC mapping | bsc-analyst | Task 1 | `_workspace/02_bsc_mapping.md` |
| 2b | SWOT analysis | swot-specialist | Task 1 | `_workspace/03_swot_analysis.md` |
| 3 | Vision & Mission + Roadmap | strategy-writer | Tasks 1, 2a, 2b | `_workspace/04_vision_mission.md`, `_workspace/05_strategy_roadmap.md` |
| 4 | Strategy review | strategy-reviewer | Tasks 1, 2a, 2b, 3 | `_workspace/06_review_report.md` |
Tasks 2a (BSC) and 2b (SWOT) execute **in parallel**. Both depend only on Task 1 (OKR), so they can start simultaneously.
**Inter-agent communication flow:**
- okr-designer completes → sends OKR system to bsc-analyst; sends strategic assumptions to swot-specialist
- bsc-analyst completes → sends strategic blind spots to swot-specialist; sends KPI system to strategy-writer
- swot-specialist completes → sends TOWS strategy priorities to strategy-writer
- strategy-writer completes → sends all documents to strategy-reviewer
- strategy-reviewer cross-verifies all deliverables. When RED Must Fix items are found, sends revision requests to the relevant agent → rework → re-verify (up to 2 iterations)
### Phase 3: Integration and Final Deliverables
1. Verify all files in `_workspace/`
2. Confirm that all RED Must Fix items from the review report have been addressed
3. Report the final summary to the user:
- OKR Design Document — `01_okr_design.md`
- BSC Mapping Table — `02_bsc_mapping.md`
- SWOT Analysis Report — `03_swot_analysis.md`
- Vision & Mission Statement — `04_vision_mission.md`
- Strategy Execution Roadmap — `05_strategy_roadmap.md`
- Review Report — `06_review_report.md`
## Execution Modes by Request Scope
| User Request Pattern | Execution Mode | Agents Deployed |
|---------------------|---------------|----------------|
| "Build a strategy framework," "Full strategy system" | **Full Pipeline** | All 5 agents |
| "Just design OKRs" | **OKR Mode** | okr-designer + reviewer |
| "Run a SWOT analysis" | **SWOT Mode** | swot-specialist + reviewer |
| "Write the vision and mission" (existing analysis available) | **Document Mode** | strategy-writer + reviewer |
| "Review this OKR" | **Review Mode** | reviewer only |
| "Create OKR and BSC" | **Analysis Mode** | okr-designer + bsc-analyst + reviewer |
**Existing file utilization**: When the user provides existing files (OKR, SWOT, etc.), copy the file to the appropriate numbered position in `_workspace/` and skip the corresponding agent's phase.
## Data Transfer Protocol
| Strategy | Method | Purpose |
|----------|--------|---------|
| File-based | `_workspace/` directory | Store and share major deliverables |
| Message-based | SendMessage | Real-time key information transfer, revision requests |
File naming convention: `{order_number}_{deliverable_name}.md`
## Error Handling
| Error Type | Strategy |
|-----------|----------|
| Insufficient organization info | Design hypothesis-based OKR using industry benchmarks, tag with "HYPOTHESIS-BASED" |
| Web search failure | Proceed with general knowledge, tag with "DATA LIMITED" |
| Agent failure | Retry once → if still failing, proceed without that deliverable and note the omission in the review report |
| RED found in review | Send revision request to the relevant agent → rework → re-verify (up to 2 iterations) |
| OKR-SWOT contradictiTrust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (1)
name: license-strategist description: "IP license strategist. Develops IP asset monetization strategies, cross-licensing, technology transfer, and open source strategies, and designs license agreement
Gates applied: no_behavioural_pass.
459e1bb8f76efull audit observations/trust-audit/skill/revfactory__strategy-framework.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 459e1bb8f76e | SAFE | B | 89 | first audit |
Questions
Is Strategy Framework safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Strategy Framework access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (459e1bb8f76e), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.