oft-spec-driven-development

Automates turning GitHub issues or Jira tickets into OpenFastTrace changeset plans with prioritized, traceable task lists.

4|Updated Sep 12, 2022
One-click install
npx skills add https://github.com/itsallcode/openfasttrace-intellij-plugin --skill oft-spec-driven-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oft-spec-driven-development
Source: https://github.com/itsallcode/openfasttrace-intellij-plugin/tree/main/.agents/skills/oft-spec-driven-development
Command: npx skills add https://github.com/itsallcode/openfasttrace-intellij-plugin --skill oft-spec-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supports turning new GitHub issues or Jira tickets into a complete, traceable OpenFastTrace changeset plan that aligns with project documents.

Core Features & Use Cases

  • Derives a changeset plan from issues by referencing doc/system_requirements.md, doc/design.md, and doc/design/quality_requirements.md.
  • Generates a task-list mapped to OFT IDs and linked to relevant requirements and design sections to guide implementation.
  • Maintains alignment with quality gates and governance before production code by following the prescribed workflow.

Quick Start

Provide the issue URL or title to generate a changeset plan and aligned spec/design updates.

Frequently Asked Questions about oft-spec-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changeset plan from a GitHub issue using OpenFastTrace?

Generate a structured OpenFastTrace changeset plan by providing the issue URL or title to derive a prioritized task-list mapped to OFT IDs and linked to relevant system requirements and design sections.

What is spec-driven development for traceable quality?

Spec-driven development for traceable quality automates turning new GitHub issues or Jira tickets into a structured changeset plan aligning system requirements, design, and quality requirements before code changes.

How do I create traceability links between Jira tickets and system requirements?

Create traceability links by referencing doc/system_requirements.md, doc/design.md, and doc/design/quality_requirements.md to map generated task-list items directly to relevant requirements and design sections.

Can I use this to align GitHub issues with existing quality requirements?

Yes, you can align GitHub issues with existing quality requirements by applying the changeset plan across doc/design/quality_requirements.md to maintain governance before production code changes.

Do I need pre-existing project documents to generate an OpenFastTrace changeset plan?

Yes, you need pre-existing project documents including doc/system_requirements.md, doc/design.md, and doc/design/quality_requirements.md for the tool to reference and produce traceable updates.

What's the best way to map a design document to a new development task?

The best way to map a design document to a new task is to automate changeset plan generation, which links prioritized tasks directly to relevant design sections and OFT IDs for governance.