「step」の検索結果

기능의 external behavior를 Cucumber 인수 테스트(주 검증층)로 구축 — .feature 실행으로 문서↔코드 드리프트를 구조적으로 차단, Four Layer(Steps→Protocol Driver→SUT), 태그 기반 가역 제외, 기존 JUnit 인수 테스트 이관. "인수 테스트 도입", "Gherkin을 실행 가능하게", "cucumber 셋업" 요청 시 사용. /cucumber-acceptance로 호출.

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

Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).

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

Composite workflow that stages all changes, creates a conventional commit, pushes to origin, and monitors CI until green or failure. Use when you want to commit and push in one step with CI monitoring. Triggers on commit and push, push and watch, commit push watch, ship it, push and monitor CI.

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

Knowledge base from NIST SP 800-37 Revision 2, the Risk Management Framework (RMF) for information systems and organizations. Use for the seven RMF steps (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor) and their tasks; the three-tier organization-wide risk model; authorization boundaries; the requirements-to-controls relationship; security categorization (FIPS 199/200 high-water mark) and control selection/tailoring (SP 800-53/53B baselines); assessment, the authorization decision and risk acceptance, continuous monitoring and ongoing authorization; the security/privacy distinction; and supply chain risk management. This is the security-and-privacy-risk-governance edge of systems engineering — it governs how much protection and whether to accept residual risk, complementing the disciplines that decide how protection is built. Does NOT reproduce the SP 800-53 control catalog or its baselines, the FIPS impact tables, or the ISO/IEC/IEEE 15288 process text; it names and routes to them rather than restating them.

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

Knowledge base from the SD-22 DMSMS Guidebook (DSPO, FY24 working draft). Use for managing Diminished Manufacturing Sources and Material Shortages (DMSMS) and obsolescence across a long-lived system's life cycle: the five-step process (Prepare, Identify, Assess, Analyze, Implement) plus the Strategize overlay; standing up a DMSMS Management Team (DMT) and Management Plan (DMP); risk-based monitoring and surveillance (the risk cube, predictive tools, vendor surveys, GIDEP/DLA PDNs, critical-materials analysis); health assessments and resolution timing; costing and selecting resolutions (life-of-need buys, substitutes, redesign, technology refreshment) by AoA/BCA; and budgeting/executing resolutions through modification funding and the ECP process. Defense-sustainment / DoD-acquisition framing throughout. Does NOT teach general systems engineering, parts-management standards, or contracting law in depth, and does not reproduce DoD policy text or the source's tables and figures.

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

Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.

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

Knowledge base from NIST Cybersecurity Framework (CSF) 2.0. Use for cybersecurity risk management, GOVERN, IDENTIFY, PROTECT, DETECT, RESPOND, RECOVER, Organizational Profiles, CSF Tiers, supply chain risk, enterprise risk management, incident response. Covers the CSF 2.0 document only; does not cover specific SP 800-53 controls, NIST RMF system authorization steps, or sector-specific regulations.

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

Knowledge base from the Expanded Guidance for NASA Systems Engineering (NASA/SP-2016-6105-SUPPL, Volume 1, March 2016) — the practitioner-depth supplement to the NASA SE Handbook. Use for the load-bearing mechanics the handbook compresses: the SE Engine's per-phase cadence and the iterative-vs-recursive distinction, the AS9100 crosswalk, life-cycle tailoring vs. customization and the Compliance Matrix, the recursive system-design consistency loop (ConOps vs. Operations Concept, requirement flow/type/ownership, successive refinement), product realization (verify/qualify/accept/certify cardinality, protoflight, 'test the way we fly' coverage, two-form transition), and the crosscutting technical-management procedures (six-step scheduling, cost-estimating method selection, JCL, interface document family, RIDM/CRM, CM baselines, EVM arithmetic, MOE/MOP/KPP/TPM, the three required leading indicators, and the decision-analysis method catalog). This is the DEPTH layer — it deliberately does NOT restate the base definitions; pair it with the nasa-se-handbook pack. Scope: NASA space-flight SE practice (Vol 1 Practices); thin on the Vol 2 process-appendix detail, on non-NASA/commercial life cycles, and on software-engineering methodology.

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

Knowledge base from the GAO Technology Readiness Assessment Guide (GAO-20-48G, 2020). Use for evaluating technology maturity in acquisition programs and projects: Technology Readiness Levels (TRL 1–9) and related scales (MRL, IRL), identifying Critical Technology Elements (CTEs), the five-step process for a high-quality TRA, the four characteristics of a reliable TRA (comprehensive, well-documented, credible, defensible), Technology Maturation Plans (TMPs), and using TRA results in knowledge-based, milestone decisions. Assessment/maturity oriented: it measures readiness and frames risk — it is not a full SE process model, cost-estimating, or schedule guide (see sibling packs for those).

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

Knowledge base from the GAO Cost Estimating and Assessment Guide (GAO-20-195G). Use for program cost estimating: the four characteristics of a reliable estimate (comprehensive, well documented, accurate, credible) and the 18 best practices; the 12-step cost estimating process (purpose, plan, technical baseline, WBS, ground rules and assumptions, data, point estimate, sensitivity, risk/uncertainty, document, present, update); estimating methods (analogy, parametric, engineering build-up, learning curves); Monte Carlo risk/uncertainty analysis, confidence levels and contingency; auditing and validating an estimate against the characteristics; earned value management (EIA-748, BCWS/BCWP/ACWP, CPI/SPI/TCPI, EAC, PMB, IBR); and specialized techniques (software cost estimating, learning curves, Analysis of Alternatives, WBS templates, the Green Book internal-control framework). This is the cost-estimating companion to the GAO Schedule and Technology Readiness Assessment guides. Does not cover schedule estimating/risk in depth (see the GAO Schedule Assessment Guide), agency-specific cost models, or the full text of referenced standards (EIA-748, MIL-STD-881D, the Green Book) — these are named, not reproduced.

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

Knowledge base from the NASA Cost Estimating Handbook (CEH) v4.0. Use for NASA's 12-step, three-part cost estimating process (Project Definition, Cost Methodology, Cost Estimate); the WBS, CADRe, and ONCE data backbone; estimating methodologies (analogy, parametric/CER, engineering build-up, EVM, Delphi); ground rules and assumptions, data normalization and inflation (BY/CY/RY); the point-estimate-to-S-curve cost-risk chain and Unallocated Future Expense (UFE) reserves; Joint Cost and Schedule Confidence Level (JCL) analysis via probabilistic cost-loaded schedules; decision-support analyses (sensitivity, trade studies, make/lease-vs-buy, affordability, CAIV); and economic analysis (discounting, NPV, OMB Circular A-94). The cost-estimating complement to NASA's SE and risk packs. Does NOT reproduce the handbook's tool-specific procedures, worked examples, or appendix-depth methods (it names the appendices), nor cover full DoD/GAO cost guides, schedule construction, or formal risk management beyond the cost interface.

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

Knowledge base from the DoD Risk, Issue, and Opportunity (RIO) Management Guide for Defense Acquisition Programs (OUSD R&E, Sep 2023 incl. Change 2.2). Use for the defense-acquisition mechanics of program risk management: the RIO definitions (risk/issue/opportunity), the five-step risk process (plan-identify-analyze-mitigate-monitor), 1-5 likelihood/consequence scoring and the 5x5 risk matrix, the four mitigation options (accept/avoid/transfer/control), burn-down plans, issue management (probability=1), opportunity management toward should-cost, cross-program/interface risk, tailoring RIO to the six AAF acquisition pathways (UCA/MTA/MCA/Software/DBS/Services), specialized methods (RMF, MBCRA/Cyber Table Top, Agile metrics, FMECA, ITRA/DTRAM), and institutionalizing RIO via the PRMP, boards (RMB/JRMB/ROMB/RWG), tools, tiered roles, and WBS/IMP/IMS/EVM/TPM integration. This is the DoD-acquisition complement to nasa-risk (general CRM/RIDM theory) and dau-se-guidebook (the SE process frame). Does NOT teach general risk theory from scratch, and defers specialized risk regimes (system safety/ESOH, HSI, detailed cyber/RMF, spectrum) to their own DoD instructions and the relevant packs.

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

Knowledge base from the FAA System Safety Handbook (Dec 30, 2000). Use for system safety as a specialty within systems engineering: the five-step safety risk management process (mandated by FAA Order 8040.4 and the AMS), the severity-by-likelihood risk matrix and acceptance bands, the Safety Order of Precedence, system-description models (5M, SHEL(L)), the hazard-analysis activities (PHL/PHA/RHA/SSHA/SHA/O&SHA/HHA), integrated system hazard analysis, the analysis techniques (FTA, FMEA/FMECA, Fault Hazard, Common Cause, Sneak Circuit, Energy Trace), closed-loop hazard tracking (Safety Action Record), and the specialty domains the handbook covers — acquisition-lifecycle safety and contracting (OSA/CSA/SSPP/ISSPP), software safety (control-capability ranking, SHCM, DO-178B), test & evaluation safety, facilities safety, commercial launch safety (AST licensing, expected casualty, MPL/DAMP), system safety training, and Operational Risk Management (ORM) with human/organizational factors. Scope limits: this is a year-2000 FAA how-to; it predates the modern FAA/ICAO Safety Management System (SMS) and Just Culture regulatory frameworks, and many cited orders, advisory circulars, and launch-licensing rules have since been restructured. It is FAA/NAS-centric, leans on MIL-STD-882C, and does not define the SE life-cycle processes themselves (use nasa-npr-7123 / dau-se-guidebook) or reproduce third-party standard text (MIL-STD-882, DO-178B, ISO/IEC/IEEE).

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

Resolución estructurada de problemas en 6 pasos: Definición del problema, objetivos, lluvia de ideas, evaluación, implementación y revisión.

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

Структурированное решение проблем в 6 шагов: Определение проблемы, постановка целей, мозговой штурм, оценка, реализация и проверка результатов.

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

六步骤结构化问题解决：问题定义、目标设定、头脑风暴、方案评估、实施与效果复盘。

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

6つのステップによる構造化問題解決：問題の定義、目標設定、ブレインストーミング、評価、実行、効果検証。

Structured 6-step procedure for improving, renovating, or rebuilding existing pipelines, individual project folders, documentation structures, or software stacks. Addressable as "pipeline optimizer" (for whole topic pipelines, e.g. a software, research, or game-dev pipeline) or "project-folder optimizer" (for individual project folders within a pipeline, e.g. a single software tool or paper project). Triggers on tasks like "improve pipeline X", "optimize the stack", "rebuild Y", "renovation", "pipeline refactoring", "clean up project folder", "improve folder structure", "unify conventions", "documentation consolidation", "integrate into existing system", or any substantial intervention in established structures. Delivers building-stock analysis, purpose clarification, ideal sketch, gap plan, empirical pain-point identification, and retests with fresh subagents. Prevents parallel standards, duplication, and pipeline breaks.

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

Prepares the contents of a dated backup of a custom skills folder and drafts a session journal entry, both for the user to save, so work can be resumed after a crash, a context loss or a skills wipe. Returns the copy action list, backup manifest, journal entry, resume summary and a restore plan whose steps the user confirms one by one and carries out. Use when the user asks to "back up my skills folder", "checkpoint this session", "write the session journal", "where did we leave off last time", "restore my skills from the last backup" or "take a safety copy before I edit this skill". Do not use for holding individual file changes for approval during ordinary work, use no-delete-guardrail instead. Drafts for human review; never approves, authorises or signs off.

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

Reads an accounts payable exception list (mismatches, possible duplicates, missing or exhausted purchase orders, missing receipts, vendor or bank detail differences) with any invoice, purchase order and receipt data supplied, and returns a DRAFT action sheet: per line, the exception as stated, the facts as read, the difference where both sides exist, one proposed next action for the accounts payable clerk to perform, who or what it needs, and a draft query, with UNKNOWN wherever the data is silent. Use when the user asks to "review these invoice exceptions", "work through the AP exception queue", "what should I do with these blocked invoices", "propose next steps for the three-way match failures" or "sort out the duplicate and missing PO invoices". Do not use for a purchase order log screened for anomalies, use purchase-order-anomaly-review instead; for an expense claim against policy, use expense-policy-precheck. Drafts for human review; never approves, authorises or signs off.

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

Audit and repair a kohya-style LoRA dataset before training. Use when the user asks to check, validate, inspect, fix, clean, 体检, or 修 a dataset, captions, or tags. Inspect image count, repeats and step budget, resolution and aspect buckets, duplicates, corrupt or non-RGB images, missing or empty captions, trigger consistency, and tag-frequency hygiene. Return a structural PASS, WARN, or FAIL report and apply only confirmed fix_dataset.py actions, dry-run first with displaced originals quarantined.

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

Resolve complex or high-impact problems when the cause, solution path, requirements, or proof boundary is genuinely uncertain. Use when work needs evidence-led diagnosis, consequential design or implementation, or a completion audit; do not trigger merely because work has multiple steps, or for simple facts, fully specified routine changes, or pure creative generation.

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

Work leads in Telegram: find prospects by topic, keep only those who self-mentioned it, resolve their handle including through shared groups, pitch personalized and grounded in real templates, run a two-step scheduling close, triage follow-ups, and capture everyone in the CRM. Triggers: "find leads for <topic>", "pitch this prospect", "run outreach".

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

Package a contribution (gist, script, fix or skill) as a product instead of a bare snippet: README with problem and result, install steps, a test, license, honest limits and a clear entry point. Use before publishing a gist, sharing a fix or releasing a slice of internal tooling. Triggers: /pack, package this properly, make it a product, ship it with quality.

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