cipherpol-aegis

Plugin cipherpol-aegis from marketplace cipherpol in hndhr/software-dev-agentic. Commands read from the repo's manifest — 1 month ago.

Skills (48)

• aegis-cipherpol-status

  Full CipherPol health check — shows platform, project, plugin versions, KMS connectivity, and knowledge coverage for the current project.

• aegis-codebase-explore

  Execute one codebase search pass for a given symbol, pattern, or path. Encapsulates Grep-before-Read discipline. Call once per lookup target; call twice for two independent targets.

• aegis-detect-platform

  Detect the platform and project for the current session. Returns platform=<kms_id> and project=<id> for use in KMS calls.

• aegis-installer-doctor

  Audit the CipherPol plugin setup in a downstream project — checks plugin installation, marketplace config, settings, CLAUDE.md markers, and GitHub CLI auth.

• aegis-installer-setup-project

  Set up the project environment following the platform's setup reference.

• aegis-kms-load

  Load knowledge for a domain scope — given discipline + artifact + topic coordinates, scans the TOC, selectively fetches matching nodes, optionally checks the project tier, and explores the codebase. Call once per knowledge domain; call twice for two domains.

• aegis-kms-lookup

  Look up KMS nodes from free-text names. One kms_list scan builds the slug map; exact match is tried first per name; kms_query handles ambiguous or non-canonical names. Returns resolved content + unresolved flags. Call once per batch.

• developer-adjust-ticket

  Adjust one or more locally fetched Jira ticket files based on session discussion. Gathers context per ticket then writes the Session Adjustment section for each.

• developer-backend

  Build the Domain and Data layers for a feature — entities, repository interfaces, use cases, mappers, datasources, and repository implementations. Calls skills directly in layer order.

• developer-brainstorm-build-feature

  Brainstorm then build a feature — invokes /developer-brainstorming (explore context + clarify + design + spec approval), then on approval invokes /developer-build-feature to execute against the written spec.

• developer-brainstorming

  Explicit design/brainstorming entry point — run ONLY when the user directly asks to brainstorm or turn an idea into a concrete design and spec before implementation, or when invoked by /developer-brainstorm-build-feature. Do NOT auto-trigger from general feature requests, questions, or incidental id

• developer-breakdown-requirement

  Turn a requirement into Jira tickets — accepts a PRD, Figma UI stack, or nothing (elicited conversationally), clarifies scope through discussion until it converges, then produces either a multi-ticket breakdown under a parent, OR a single enriched ticket (scaffold an empty ticket or re-evaluate an a

• developer-build-feature

  Explicit feature-execution entry point — run ONLY when the user directly invokes it with a run_dir or an approved plan/spec document, or when routed from /developer-plan-build-feature, /developer-brainstorming, or /developer-brainstorm-build-feature. Do NOT auto-trigger from general "build"/"impleme

• developer-build-from-ticket

  One-shot feature build from a Jira ticket. Non-interactive — designed for remote AI tools (CI job, API caller). Pass a Jira ticket key or URL as the only argument. Fetches the ticket, derives planning inputs, runs the convergence planning loop automatically, builds, then cleans up run state.

• developer-clear-runs

  Remove all strategist run state from .claude/agentic-state/developer/feature-plans/. Clears stale state.json and stateholder-contract.md artifacts left by feature-strategist and other strategists.

• developer-data-create-datasource

  Create a data source (remote or local) in the data layer.

• developer-data-create-mapper

  Create a mapper that converts DTOs to domain entities and vice versa.

• developer-data-create-repository-impl

  Create the repository implementation that bridges domain interfaces and data sources.

• developer-debug-add-logs

  Add strategic debug logs to trace execution flow or diagnose a bug.

• developer-debug-remove-logs

  Remove all debug logs added by developer-debug-add-logs.

• developer-debug-report-ts

  Investigate a TypeScript/mobile issue report end-to-end — classify the issue, gate on available data, fetch Firebase Crashlytics events and Loki logs, trace the root cause through Clean Architecture layers, propose solutions, and implement the chosen fix.

• developer-debug

  Explicit debugging entry point — run ONLY when the user directly asks to debug or investigate a specific bug, or when invoked by /developer-plan-feature or /developer-groom-ticket. Do NOT auto-trigger from incidental error messages or mentions of a bug. Accepts an optional bug description, collects

• developer-domain-create-entity

  Create a domain entity class.

• developer-domain-create-repository

  Create a domain repository interface.

• developer-domain-create-service

  Create a domain service for business logic that spans multiple entities or use cases.

• developer-domain-create-usecase

  Create a domain use case.

• developer-extract-sysdesign

  Extract a System Design document from one or more screen or component entry points, or consolidate existing system designs into a flow design. Single file → Screen or Component System Design. Multiple files → parallel extraction then Flow System Design (if designs are related). Multiple existing .md

• developer-fetch-figma

  Explicit Figma-fetch entry point — run ONLY when the user directly asks to fetch Figma frames, or when invoked by /developer-plan-feature or /developer-breakdown-requirement. Do NOT auto-trigger from incidental Figma links or mentions of a design. Fetches frames via Figma MCP, groups them by visual

• developer-groom-ticket

  Consult on a locally fetched Jira ticket — drives a back-and-forth discussion to clarify the problem statement, identify work items, surface decisions and open questions, then writes the grooming outcome to the ticket via the developer-adjust-ticket workers. Run before /developer-plan-feature or /de

• developer-issue

  Create or pick up a GitHub Issue — opens the issue, creates a branch, and updates the local backlog.

• developer-jira-ticket

  Create Jira tickets under an epic from a platform breakdown list — fetches PRD and optional Figma context, generates requirement-focused descriptions, and creates tickets via Atlassian MCP.

• developer-plan-build-feature

  Plan then build a feature — invokes /developer-plan-feature (figma fetch + convergence planning loop + approval), then on approval invokes /developer-build-feature to execute the approved plan.

• developer-plan-feature

  Explicit feature-planning entry point — run ONLY when the user directly asks to plan a feature, or when invoked by /developer-plan-build-feature. Do NOT auto-trigger from incidental mentions of planning. Resolves external inputs (Jira, PRD, Figma, local .md), gathers intent via developer-feature-int

• developer-pres-create-component

  Create a reusable presentational component that takes plain domain entities with no state-management awareness.

• developer-pres-create-screen

  Create the Screen / View that binds to the StateHolder and renders state.

• developer-pres-create-stateholder

  Create the StateHolder (BLoC / ViewModel / Presenter) for a feature screen.

• developer-pres-resolve-design

  Resolve UI element descriptions against the KMS design-system catalogs (discipline=design, area=design-system). Returns a Design System Bindings table (matched) and a Custom Widgets table (unmatched). Soft-fails with empty tables if KMS has no design-system area for the platform.

• developer-push-tickets

  Push local ticket files to Jira — either create fresh tickets under an epic from a run directory, or update an existing Jira ticket with the content of a local TICKET-NNN.md file.

• developer-rfc

  Generate an RFC and ticket breakdown from a Jira Epic + PRD + optional Design. Fetches inputs, runs the Clean Architecture convergence planning loop, then writes <epic-slug>-rfc.md and <epic-slug>-breakdown.md.

• developer-test-create-data

  Create unit tests for repository implementations and mappers.

• developer-test-create-domain

  Create unit tests for domain use cases and services.

• developer-test-create-mock

  Generate mock classes for domain interfaces used in tests.

• developer-test-create-presentation
• developer-test-procedure
• developer-type-check
• developer-validate-artifact-output
• qa-generate-automation
• qa-generate-testcase

Subagents (38)

• developer-adjust-ticket-gather-worker

  Reads a local Jira ticket file and extracts its ID and Acceptance Criteria. Returns a partial context block (TICKET_PATH, TICKET_ID, ACCEPTANCE_CRITERIA) — no user interaction. Invoked by /developer-adjust-ticket and /developer-groom-ticket.

• developer-adjust-ticket-write-worker

  Writes the Session Adjustment section to a local Jira ticket file using pre-gathered session context. Handles existing section replacement and custom subsection preservation. Invoked by /developer-adjust-ticket and /developer-groom-ticket.

• developer-app-planner

  Explore app-layer wiring for a given feature — discovers existing DI registration, route registration, and module registration patterns. Returns structured findings for feature-planner to synthesize. Writes findings to run_dir only — no codebase writes.

• developer-backend-worker

  Build the Domain and Data layers for a feature — entities, repository interfaces, use cases, mappers, datasources, and repository implementations. Calls skills directly in layer order. No sub-agents.

• developer-breakdown-strategist

  Clarifies requirements for a Jira ticket through discussion, then produces either a multi-ticket breakdown (breakdown mode) or a single enriched ticket (single mode — scaffold an empty ticket or re-evaluate an already-built one). Reads PRD and optional Figma context, elicits requirements conversatio

• developer-data-planner

  Explore the Data layer for a given feature — discovers existing DTOs, mappers, data sources, and repository implementations. Returns structured findings for feature-planner to synthesize. Writes findings to run_dir only — no codebase writes.

• developer-debug-log-worker

  Add or remove debug instrumentation logs in source files. Use when developer-debug-worker or developer-debug-strategist identifies exact file paths and method names that need runtime tracing. Pass mode=add with an instrumentation brief, or mode=remove to strip all debug logs before committing.

• developer-debug-strategist

  Route a bug report to the right debug worker(s). Use when the failure location is unknown, spans multiple modules, or requires coordinating more than one specialist worker.

• developer-debug-ts-classify-worker

  Classify a Talenta mobile issue report (api | anr | crash | other) and trace its root cause through Clean Architecture layers. Accepts two modes — classify (returns a Classification block from static code analysis) and analyze-root-cause (returns Code Analysis, Root Cause, and Proposed Solutions aft

• developer-debug-ts-firebase-worker

  Fetch Firebase Crashlytics events for a Talenta issue report. Given a classification type, app ID, version/OS filters, and optional custom-key targets (user_id/user_email/company_id), queries topVersions, topOperatingSystems, topIssues, and batch event records to return a structured findings block o

• developer-debug-ts-fix-worker

  Implement a chosen fix for a Talenta mobile issue. Given a structured fix_brief (chosen solution, implicated file paths, change description) and a project_path, reads the target files, implements the localized fix, and validates output. For large multi-layer fixes, emits a handoff block instructing

• developer-debug-ts-log-analyzer-worker

  Analyze Mekari Log entries to build a user activity timeline, identify errors, find root causes, and propose code fixes. Use when raw log JSON from Grafana Loki (via developer-debug-ts-loki-query-worker) is available and you want to understand what happened during a user session. Works with Flutter

• developer-debug-ts-loki-live-tracking-worker

  Query Talenta live tracking / geolocation logs from Grafana Loki. Use when the user wants to investigate GPS/location events, MQTT messages, tracking errors, or user position activity by providing a user_id and a time range. Queries the geolocation-service mqtt-subscriber container. Handles large ti

• developer-debug-ts-loki-query-worker

  Query Talenta production logs from Grafana Loki. Use when the user wants to investigate user activity, errors, API calls, or any log events by providing an encrypted user property (email, phone, etc.) and a time range. Handles large time ranges automatically by chunking into smaller windows.

• developer-debug-worker

  Trace a runtime error or unexpected behavior through the Clean Architecture layers to its root cause. Use when you have an error, stack trace, or something not working as expected.

• developer-doc-resolve-worker

  Resolves a document source — Jira issue URL/key, Confluence page URL/ID, generic URL, or local file path — into plain text content. Returns a structured result block (with issue key and type for Jira). Called by /developer-breakdown-requirement before the breakdown strategist runs.

• developer-domain-planner

  Explore the Domain layer for a given feature — discovers existing entities, repository interfaces, use cases, and domain services. Returns structured findings for feature-planner to synthesize. Writes findings to run_dir only — no codebase writes.

• developer-feature-convergence-strategist

  Validates planner findings each round, drives convergence, and synthesizes plan.md + context.md once all required layers are covered.

• developer-feature-intent-strategist

  Gathers feature intent interactively or from pre-filled fields. Detects existing runs, extracts Figma URLs from raw inputs, and returns a Decision block for the entry skill to route on. Also supports pre-plan mode — explores module structure to generate scope candidates when the user's goal is uncle

• developer-feature-worker

  Execute an approved feature plan for Domain, Data, Presentation (StateHolder), and App layers — reads plan.md, calls skills in layer order, validates each artifact inline. UI layer (Screen/Component/Navigator) is handled by developer-ui-worker after this worker completes. Invoked by /developer-build

• developer-figma-fetch-worker

  Fetch a single Figma node via Figma MCP — writes a compact semantic .md and downloads a screenshot. JSX is extracted for semantic fields but not written to disk. Returns a compact summary block to the caller.

• developer-figma-group-worker

  Groups fetched Figma frames by visual structure, synthesizes one UIStack per screen/overlay cluster, and checks design system availability. Called after all developer-figma-fetch-worker agents complete for a fetch directory.

• developer-figma-validate-worker

  Validate and expand Figma URLs before fetching — classifies each URL as invalid, single frame, or multi-frame container (section/group/page), expands containers into individual frame URLs, creates figma_fetch_dir, and writes pending-frames.json. Returns a compact block with directory path and frame

• developer-groom-strategist

  Consults on a Jira ticket against the codebase — reads the ticket and explores the codebase directly to clarify the problem statement, identify work items, surface decisions and open questions. Returns structured decision blocks for the calling skill to drive the discussion loop. Invoked only by the

• developer-jira-ticket-worker

  Creates Jira tickets under an epic from a platform breakdown list — parses platform/scope/duration, fetches PRD and optional Figma design context, generates requirement-focused descriptions, and creates tickets via Atlassian MCP. Invoked only by /developer-jira-ticket.

• developer-pres-planner

  Explore the Presentation and UI layers for a given feature — discovers existing StateHolders, screens, and components. Returns structured findings for feature-planner to synthesize. Writes findings to run_dir only — no codebase writes.

• developer-push-new-tickets-worker

  Reads local TICKET-NNN.md files and creates new Jira issues under a parent — detects parent issue type (Epic/Story/Task), validates ticket type compatibility, then calls createJiraIssue for each ticket. Invoked only by /developer-push-tickets.

• developer-rfc-writer

  Pure writer. Receives Epic + PRD + Design + converged plan.md + context.md inline, then writes <epic-slug>-rfc.md and <epic-slug>-breakdown.md to .claude/agentic-state/developer/rfc/. No codebase reads, no user interaction.

• developer-sync-ticket-worker

  Syncs a local TICKET-NNN.md file to an existing Jira ticket — fetches the current Jira ticket content, diffs it against the local file, shows the user what will change, and updates on confirmation. Invoked by /developer-push-tickets and by /developer-breakdown-requirement (single-ticket mode).

• developer-sysdesign-component-extract-worker

  Extract a Component System Design document from a single component file (manager, service, repository, datasource, etc.) — reads the public interface, traces dependencies, and produces a structured system design covering purpose, public interface, dependencies, data model, high-level design, and key

• developer-sysdesign-consolidate-worker

  Consolidate multiple Screen and/or Component System Design documents into a single Flow System Design — checks relevance first, then deduplicates APIs, merges data models, builds a combined layer diagram, and traces cross-participant data flows. Invoked by /developer-extract-sysdesign after extracti

• developer-sysdesign-extract-worker

  Extract a Screen System Design document from a single screen entry point — traces through presentation, domain, and data layers to produce a structured system design covering API, data model, layer diagram, data flows, and UI stack. Invoked by /developer-extract-sysdesign.

• developer-test-worker

  Route test creation requests to developer-test-procedure — identifies the CLEAN layer from the target file path and invokes the procedure skill. Entry point for unit test generation across all platforms.

• developer-ticket-write-worker

  Writes approved ticket data as local markdown files — receives one or more ticket objects and writes one TICKET-NNN.md file per ticket to the run directory. Invoked only by /developer-breakdown-requirement.

• developer-ui-worker

  Execute the UI layer of an approved feature plan — Screen, Component, and Navigator artifacts only. Spawned by /developer-build-feature after developer-feature-worker emits Layers Complete. Starts with a clean context: loads plan.md, context.md, stateholder-contract, and Figma references fresh.

• developer-uistack-align-worker

  Analyze a figma-uistack-<screen-slug>.md against the project's design system — rename components, correct tokens, and flag gaps. Revises the file in place and returns a compact report to the caller.

• qa-automation-worker

  Generates Maestro YAML automation scripts from mobile UI test case CSVs. One YAML file per feature area, written to /test-automation/maestro/ in the downstream project.

• qa-testcase-worker

  Generates and maintains mobile UI test cases from Jira tickets, PRDs, or Figma designs. Handles create and regenerate modes. Writes .csv to /test-cases/ and posts Jira comments.

Similar plugins