「sdlc」の検索結果

Commission a project to the Assured (Method 2) SDLC bundle — install plugin, scaffold programs.yaml, set granularity and regulatory context, configure change-impact-gate.

日本語の概要は準備中です。原文の説明を表示しています。

Shared conventions for every SDLC development-phase architect agent: hard rules, code quality bar, workflow steps (superpowers invocation, spec reading, codebase exploration, verification), and the report/compact-summary contract. Architects load this skill first, then apply their stack-specific instructions on top.

日本語の概要は準備中です。原文の説明を表示しています。

Review Kanban handoffs and route verified outcomes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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".

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Pick a Linear PBI, spec it, assemble it, then hold at the gate with a Boeing list for HITL clearance. Does NOT ship.

日本語の概要は準備中です。原文の説明を表示しています。

Pick the next task from the Linear backlog with the best speed/value ratio

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Produce written specs and atomic PBIs that an implementation agent can execute independently. Authors specs and Linear issues.

日本語の概要は準備中です。原文の説明を表示しています。

Create, reverse-engineer, or update living feature specs following the spec-anchored methodology.

日本語の概要は準備中です。原文の説明を表示しています。

Implement features, fix bugs, and keep the codebase healthy and maintainable. Works from a defined PBI, issue, or task description.

日本語の概要は準備中です。原文の説明を表示しています。

Triage the content corpus against the latest GSC snapshot and produce a prioritized refresh report. Read-only: reports, never edits.

日本語の概要は準備中です。原文の説明を表示しています。

Dev-Critic loop: implement, review, fix — repeat until clean

日本語の概要は準備中です。原文の説明を表示しています。

Perform an adversarial review of the current uncommitted changeset, validating it against project contracts and architectural intent.

日本語の概要は準備中です。原文の説明を表示しています。