166 skills · sorted by relevance
Scaffold a new iOS app with SDLC and submission-safe defaults — diffable project files, app + test targets, deployment-target policy, a git-stamped build number, and the Info.plist keys the pre-flight checker wants so the project passes TestFlight from day one. Use when starting a new iOS project.
The English summary is being prepared. Showing the original description.
Run the SDLC validation pipeline using direct tool invocations. No wrapper scripts required. Use when checking code quality before commits or PRs.
The English summary is being prepared. Showing the original description.
Run an SDLC delegated workflow via Archon. Wraps the archon CLI with project-aware defaults.
The English summary is being prepared. Showing the original description.
Check the status of running or recent SDLC delegated workflows.
The English summary is being prepared. Showing the original description.
Independently reviews deliverables handed over through Kanban, checks them against acceptance criteria and test evidence, and records an approval, actionable change request, or escalation when a human decision or external prerequisite is needed.
Use the Archon CLI to launch AI workflows on projects, inspect their results, and approve, reject, cancel, or resume runs. The skill also guides setup, configuration changes, workflow creation, and improvements to workflow prompts.
AI DevKit · Orchestrator for structured SDLC phase skills. Use when the user wants to run the full lifecycle or choose the next phase across requirements, design, planning, implementation, testing, and review.
The English summary is being prepared. Showing the original description.
Perform static application security testing with tools like Semgrep, CodeQL, and SonarQube. Identify security vulnerabilities in source code before deployment. Use when implementing secure SDLC, code review automation, or security gates in CI/CD pipelines.
The English summary is being prepared. Showing the original description.
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
The English summary is being prepared. Showing the original description.
Ground and validate SDLC product decisions with canonical evidence ledgers, immutable recorded decisions, typed provenance, and scoped action gates. Use when inspecting, maintaining, or validating product evidence ledgers.
The English summary is being prepared. Showing the original description.
Right-size, ground, and gate SDLC decisions with SNC-sized depth, said-vs-assumed write-back, an evidence ledger, honest option cards, recorded approval, and self-review. Use when running brainstorm-feature, plan-feature, design-solution, or system-design-session.
The English summary is being prepared. Showing the original description.
Audit applications and infrastructure handling payment card data against PCI DSS v4.0. Heavy emphasis on scope determination (the single most-leveraged variable) plus the engineering-relevant requirements — Req 3 (storage of CHD), Req 4 (transmission), Req 6 (secure SDLC), Req 7-8 (access), Req 10 (logging), Req 11 (testing), Req 12 (program). Use when the user mentions 'PCI,' 'PCI DSS,' 'PCI DSS 4.0,' 'payment card,' 'cardholder data,' 'CHD,' 'PAN,' 'PCI scope,' 'PCI compliance,' 'SAQ,' 'AoC,' 'attestation of compliance,' 'tokenization,' 'P2PE,' 'network segmentation for PCI,' or audits any system that stores, processes, or transmits payment card data.
The English summary is being prepared. Showing the original description.
One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".
The English summary is being prepared. Showing the original description.
Prospects companies across developer-focused tech verticals for developer marketing agency outreach. Use this skill whenever a user provides a vertical (e.g. AI Agentic, IAC, DevTools, Observability, DevOps, FinOps, AI/SDLC, AI Orchestration, or any other tech vertical) and wants a list of prospect companies to target. Also trigger when the user says "prospect for", "find companies in", "give me leads for", "build a prospect list", or provides a vertical name alongside funding stage and headcount filters. Always use this skill — never attempt prospecting without following this structured workflow. The skill finds exact-fit companies only (never adjacent), maps a real outreach signal and email pain point for each, sources every data point with a URL, and outputs a unified nine-column table: Company, URL, LinkedIn, Headcount, Signal, Signal Sources, Geography, Pain Point, Pain Point Sources.
The English summary is being prepared. Showing the original description.
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
The English summary is being prepared. Showing the original description.
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
The English summary is being prepared. Showing the original description.
Development harness plugin documentation index. Use when looking up SAM pipeline, backlog lifecycle, SDLC layers, task/plan schema, plan artifacts, quality gates, impact analysis, or dispatch schema documentation.
The English summary is being prepared. Showing the original description.
Manages the research/ knowledge base of verified tool and library research entries via knowledge-explorer.py. Commands — list (browse by category or SDLC layer), fetch-github (draft entry from GitHub repo), add (validate and route to category dir), update-append (append dated revision), generate-descriptions (repair missing or low-quality descriptions), migrate (convert inline-header entries to frontmatter). Use when browsing KB topics, adding or updating research entries, fetching GitHub repo metadata, generating descriptions in parallel via Haiku subagents, or migrating old-format entries to skill-spec frontmatter.
The English summary is being prepared. Showing the original description.
Pick a Linear PBI, spec it, assemble it, then hold at the gate with a Boeing list for HITL clearance. Does NOT ship.
The English summary is being prepared. Showing the original description.
Produce written specs and atomic PBIs that an implementation agent can execute independently. Authors specs and Linear issues.
The English summary is being prepared. Showing the original description.
Create, reverse-engineer, or update living feature specs following the spec-anchored methodology.
The English summary is being prepared. Showing the original description.
Dev-Critic loop: implement, review, fix — repeat until clean
The English summary is being prepared. Showing the original description.
Pick the next task from the Linear backlog with the best speed/value ratio
The English summary is being prepared. Showing the original description.
Lint, build, test, verify specs, commit, and push — one micro-commit to remote. Validates the working tree, verifies spec alignment, and creates an atomic save point.
The English summary is being prepared. Showing the original description.