Business & Operations

Operations, strategy, finance, sales, support, management, and planning

skills in category: 35,234
pages available: 1,469

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse business & operations skills

Showing 16,441–16,464 of 35,234 skills

Propose Kb NodeAThe nothing-fits path for the KB router. When search-kb returns unmatched (a piece of work has no home in the knowledge base), research the gap, draft a properly-shaped node at the right level (new domain, capability, or functionality) following the shelf template and functionality baseline, and emit a proposal for human review. NEVER writes to the KB — it always stops at a review checkpoint; only an approved proposal is written and re-indexed. Use when search-kb reports unmatched, or when a ...businesspythonbashVotes: 0GitHub stars: 3
Merge PrAMerge a pull request on the configured platform, switch to main, pull latest, and delete the feature branch (local and remote)businessgobashVotes: 0GitHub stars: 3
Infer Epics From CodeADerive epic boundaries for a brownfield codebase by clustering capabilities from features.yaml, enriched-capabilities.yaml, scope.yaml, and domain-selection.yaml using co-change, KB domain grouping, version tags, and ADR titles. Produces one minimal intent-epic stub per derived epic. Used exclusively by product-keeper during /codify.businessgogitVotes: 0GitHub stars: 3
Infer Enriched Capabilities From CodeAInfer per-capability enrichment (business rules, depth spectrum cap, experiential warnings) during /codify by merging KB base values from core/components/memory/knowledge/domain/{domain}.md with project-specific overrides evidenced in scan-index.json. Produces scope/garura:enriched-capabilities.yaml. Used exclusively by product-keeper in the /codify play.businessgoexpressVotes: 0GitHub stars: 3
Infer ArchitectureAInfer logical architecture from an existing codebase — module structure, design patterns, framework conventions, LLD patterns — and write architecture-inference.yaml. Used by tech-architect in the prepare play.businessgobashVotes: 0GitHub stars: 3
Enrich CapabilitiesAFor each selected capability, merge project-profile-specific overrides onto the KB base values (business rules, depth spectrum cap, experiential warnings), producing enriched-capabilities.yaml — the input to intent-epic generation.businessgosecurityVotes: 0GitHub stars: 3
Derive Systems InventoryAStage 1 skill of /arch. Walks selected capabilities, identifies the system (and any sub-systems) that serves each one, and populates the product's systems-inventory by pulling KB-grounded systems with provenance or authoring novel systems as stm_research with the required KB-extension shape. Output is the inventory every later /arch stage reads.businessapiVotes: 0GitHub stars: 3
Author Vision SeedAAuthor the /vision seed of the product model — a detailed domain grounding doc and directional capability grounding docs — straight to the live model, and emit the matching spine-delta (domain + capability entries, status proposed, detail directional, and the directional profile block) as structured data in the seed manifest. Generative artifact production for the /vision play. Under direct-model-write (ADR 026) it writes ONLY the per-node docs (domain.md, capability.md) in place, skip-if-exi...businessgobashVotes: 0GitHub stars: 3
VisionATurn a business goal into the seed of the product model — a detailed domain grounding doc, directional capability grounding docs, the spine entries that wire them, and a directional product profile — written directly in place on the live model. The entry play of the strategic (shaping) pipeline in the ProductOS command model — the CXO conversation. Use when starting a new product area from a business goal, before /understand and /shape. Opens no delivery issue of its own beyond the strategy-p...businesspythongoVotes: 0GitHub stars: 3
UnderstandADetail one capability that /vision seeded — promote its grounding from directional to detailed, create and detail its functionalities, set the capability''s own NFR + compliance needs, and roll those needs up into the product profile, firming the box and recording a decision for any out-of-box move. The product-manager step of the ProductOS strategy pipeline, after /vision and before /shape — the last detailing step. Opens no delivery issue.businesspythonbashVotes: 0GitHub stars: 3
ShapeASelect what to build in one domain and compose it into deliverable verticals — confirm or prune its capabilities against the firmed profile + KB, select which of the functionalities /understand created to build now, create the personas and user journeys, and bundle the functionalities into vertical slices, each behind a user-facing surface scaffolded slice by slice. The product-owner step of the ProductOS strategy pipeline, after /vision and /understand. Selects against the profile but never ...businesspythonrustVotes: 0GitHub stars: 3
RoadmapAPlan the product''s vertical slices into a build sequence — order the slices /shape produced across all domains, resolve their dependencies, and estimate each one''s effort, writing only the plan onto each slice, directly in place on the live model. The planning play in the ProductOS command model, after /shape. Reads the slices to judge order and effort but writes only the plan (order, effort, dependencies). Closes the strategy pipeline through the end PR. Opens no delivery issue.businesspythongoVotes: 0GitHub stars: 3
MeasureAWrite a SLICE''s measure lens as a grounding doc (measure.md) — the delivery-measurement focus, the metrics that prove it (baseline / target / proof, triangle-primary speed/tokens/cognition), and what is out of scope — then, when all seven lens docs line up, stamp the slice realized on the spine. The DELIVER pipe of realize (runs last): it opens its own branch (start-change) and closes it (commit → propose → review → merge). Reads the hub from the spine; the single play that flips a slice to ...businesspythonbashVotes: 0GitHub stars: 3
MarketingAWrite a SLICE''s marketing lens as a grounding doc (marketing.md) — how the slice is found and reached (SEO / AEO / GEO), the accessibility bar it meets, and the reach signals worth capturing — written directly in place on the live model. The END of the FUNCTIONAL realize pipe (ux → agentic → marketing): it closes the functional pipe (commit → propose → review → merge). An internal tool answers discoverability "not applicable", plainly. Reads the hub from the spine (functionality grounding + ...businesspythonbashVotes: 0GitHub stars: 3
LearnAClose the loop: after a unit of work ships, read what actually happened — the measure lens (baseline/target/realized), the validate verdicts and fix reports, the run lens, and the delivered epic/slice status — and update the LIVING product model to match reality. Refreshes only the model''s MEANING (capability/functionality one_line, nfr_needs levels, status promotions, the grounding-doc sections learning changed) and records each material learning as an append-only decision — never the tree ...businesspythonbashVotes: 0GitHub stars: 3
GrillACut one REALIZED slice into user-testable delivery epics — the handoff from the product model to the delivery pipeline. /roadmap says which slice to build; the seven realize lenses have solved its design and /measure has stamped it realized — the marker /grill requires before it cuts. Each epic is a meaningful increment a user can open, exercise, and verify when delivered (the user-testability grain — never internal-only work), self-contained, referencing the slice''s intent and lenses, never...businesspythongoVotes: 0GitHub stars: 3
ArchAWrite a SLICE''s architecture lens as a grounding doc (architecture.md) — the components the slice threads (each in its layer, with its contract), the stack (tech + versions) behind them, and the vertical build that runs the slice end-to-end — written directly in place on the live model. The START of the NON-FUNCTIONAL realize pipe (arch → quality → run), run on a shaped slice. Every component is selected from the slice''s functionalities'' systems + the profile surfaces, never invented; the ...businesspythonbashVotes: 0GitHub stars: 3
AgenticAWrite a SLICE''s agentic lens as a grounding doc (agentic.md) — the is-it-an-agent gate, the load weights (cognitive / creative / logistical on a low→ultra scale), and the controls (guardrails, handoff). The MIDDLE of the FUNCTIONAL realize pipe (ux → agentic → marketing), run on a shaped slice. A deterministic slice comes out "not an agent", stated plainly. Reads the hub from the spine (functionality grounding + profile), never another lens. Writes only the slice''s agentic lens, in place on...businesspythonbashVotes: 0GitHub stars: 3
EvidenceA**Gate:** research-domain-context skill exists with proper input/output contracts following skill conventions. **Mandatory:** Yes **Result:** PASSbusinessVotes: 0GitHub stars: 3
VerboseAAn error message has exactly one job: get the user unstuck. It needs three components, and most shipped errors have none of them.businessgoapiVotes: 0GitHub stars: 2
MinimalAFind out what people actually struggle with by asking about their past, not their future — because everyone says yes to a hypothetical and almost nobody buys it.businessgoapiVotes: 0GitHub stars: 2
VerboseABefore writing anything, answer three questions: who reads this, what do they have to *do*, and what do they already know? The answers change the document completely, not just its tone.businessrustgoVotes: 0GitHub stars: 2
MinimalAWrite so a skimming reader gets the decision in the first two lines and the evidence only if they want it.businessgoVotes: 0GitHub stars: 2
VerboseAA metric is not a name and a number. It is a specification precise enough that two analysts who have never spoken produce the same value. Anything less guarantees a reconciliation meeting.businessgosqlVotes: 0GitHub stars: 2