jsf

Plugin jsf from marketplace jsf in jmeagher/software-factory. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• clarification

  Software factory clarification — use when gathering requirements before planning. Runs structured Q&A to produce a confirmed clarification summary.

• memory-protocol

  Software factory memory protocol — use when reading or writing factory state. Covers JSONL memory operations, well-known keys, and agent startup protocol.

• otel-tracing

  Software factory OpenTelemetry tracing — use when emitting traces for factory work. Covers root trace, phase sub-traces, and bi-directional linking.

• spec-planning

  Software factory spec and planning — use when producing a technical spec and phased implementation plan after clarification is confirmed.

• tdd-implementation

  Software factory TDD implementation — use when implementing a phase. Enforces red-green discipline and code security standards before committing.

• validation-gate

  Software factory validation gate — use when checking phase completion. Verifies automated tests pass and coordinates manual validation if required.

• workflow

  Software factory master workflow — use when starting or orchestrating a full factory run, coordinating clarification → spec → TDD implementation → validation phases.

Slash commands (4)

• /jsf:resume

  Resume a software factory workflow from the last memory checkpoint

• /jsf:start

  Start the software factory workflow for a new idea or feature request

• /jsf:status

  Show the current factory workflow state from memory

• /jsf:validate

  Run the validation gate for the current phase

Subagents (5)

• clarifier

  Runs the structured clarification dialogue for a new software request. Invoke when a new workflow starts and clarification_summary is not yet in memory.

• implementer

  Implements a single phase of the plan using TDD. Invoke with the phase identifier. Reads phase spec from implementation_plan in memory.

• planner

  Produces the technical spec and phased implementation plan after clarification is confirmed. Invoke after clarification_summary is in memory.

• reviewer

  Reviews code changes for security issues before phase commit. Invoke after phase_complete:<name> appears in memory.

• validator

  Runs the validation gate for a completed implementation phase. Checks automated tests and coordinates manual validation if needed.

Hooks (11)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/block-dangerous-bash.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/block-dangerous-git.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/block-dangerous-sql.sh

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event PreToolUse

• PostToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event PostToolUse

• SessionStart

  [ -z "${OTEL_EXPORTER_OTLP_ENDPOINT}" ] && export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317; [ -z "${SF_OTEL_ENABLED}" ] && export SF_OTEL_ENABLED=1; true

• SessionStart

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event SessionStart

• Stop

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event Stop

• SubagentStop

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event SubagentStop

• PreCompact

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event PreCompact

• Notification

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hook_tracer.py --event Notification