knowledge-synthesis-the-goal
Sub-skill of knowledge-synthesis: The Goal.
Best use case
knowledge-synthesis-the-goal is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of knowledge-synthesis: The Goal.
Teams using knowledge-synthesis-the-goal should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/the-goal/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How knowledge-synthesis-the-goal Compares
| Feature / Agent | knowledge-synthesis-the-goal | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of knowledge-synthesis: The Goal.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# The Goal ## The Goal Transform this: ``` ~~chat result: "Sarah said in #eng: 'let's go with REST, GraphQL is overkill for our use case'" ~~email result: "Subject: API Decision — Sarah's email confirming REST approach with rationale" ~~cloud storage result: "API Design Doc v3 — updated section 2 to reflect REST decision" ~~project tracker result: "Task: Finalize API approach — marked complete by Sarah" ``` Into this: ``` The team decided to go with REST over GraphQL for the API redesign. Sarah made the call, noting that GraphQL was overkill for the current use case. This was discussed in #engineering on Tuesday, confirmed via email Wednesday, and the design doc has been updated to reflect the decision. The related ~~project tracker task is marked complete. Sources: - ~~chat: #engineering thread (Jan 14) - ~~email: "API Decision" from Sarah (Jan 15) - ~~cloud storage: "API Design Doc v3" (updated Jan 15) - ~~project tracker: "Finalize API approach" (completed Jan 15) ```
Related Skills
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
workspace-knowledge-doc-contracts
Class-level workspace knowledge, LLM-wiki, repo mission contracts, stale doc references, semantic taxonomy, and knowledge-source reconnaissance.
planning-goal
Goal-Oriented Action Planning (GOAP) specialist that dynamically creates intelligent plans to achieve complex objectives. Use for multi-step tasks with dependencies, adaptive replanning, complex deployment workflows, or when a high-level goal needs systematic breakdown into achievable actions.
planning-code-goal
Code-centric Goal-Oriented Action Planning integrated with SPARC methodology. Use for feature implementation planning, performance optimization goals, testing strategy development, or any software development objective requiring systematic breakdown with measurable success criteria.
knowledge-pipeline
Workflow for maintaining workspace-hub knowledge and learning pipelines across scripts/knowledge, scripts/learning, and docs/superpowers, including indexing, archive synthesis, issue updates, and pipeline troubleshooting.
knowledge-base-builder
Build searchable knowledge bases from document collections (PDFs, Word, text files). Use for creating technical libraries, standards repositories, research databases, or any large document collection requiring full-text search.
knowledge-source-recon
Reconnaissance pattern to inventory all knowledge sources across the workspace-hub ecosystem's existing intelligence infrastructure. Maps raw sources for LLM Wiki ingestion planning. Leverages pre-built registries and indexes rather than re-scanning directories.
user-research-synthesis
Synthesize qualitative and quantitative user research into structured insights and opportunity areas
knowledge-synthesis
Combines search results from multiple sources into coherent, deduplicated answers with source attribution and confidence scoring.
knowledge-management
Create, organize, and maintain support knowledge base content to reduce ticket volume
planning-goal-metrics-success-criteria
Sub-skill of planning-goal: Metrics & Success Criteria.