~ / rigs / stsiazhkin / agent-workflow-bootstrap

stsiazhkin/agent-workflow-bootstrap

A reusable bootstrap template for specification-driven development with GitHub Copilot and Claude Code. Includes shared instructions, custom agents, prompt workflows, feature documentation templates, Jira ticket planning, agent handoffs, va

↗ GitHub ★ 0 no license updated 3mo ago project Claude CodeCodexCopilot
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~1.6k tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ npx degit stsiazhkin/agent-workflow-bootstrap/.claude ./rig-agent-workflow-bootstrap  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit stsiazhkin/agent-workflow-bootstrap/.claude/skills/plan-jira-tickets .claude/skills/plan-jira-tickets
$ npx degit stsiazhkin/agent-workflow-bootstrap/.claude/skills/refine-requirements .claude/skills/refine-requirements
$ npx degit stsiazhkin/agent-workflow-bootstrap/.claude/skills/write-feature-docs .claude/skills/write-feature-docs
$ curl -fsSL --create-dirs -o .claude/agents/doc-writer.md https://raw.githubusercontent.com/stsiazhkin/agent-workflow-bootstrap/main/.claude/agents/doc-writer.md
$ curl -fsSL --create-dirs -o .claude/agents/requirements-refiner.md https://raw.githubusercontent.com/stsiazhkin/agent-workflow-bootstrap/main/.claude/agents/requirements-refiner.md
$ curl -fsSL --create-dirs -o .claude/agents/ticket-planner.md https://raw.githubusercontent.com/stsiazhkin/agent-workflow-bootstrap/main/.claude/agents/ticket-planner.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 7,204 rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(rm -rf *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(.env)",
      "Bash(rm -rf /*)",
      "Read(./.env.*)",
      "Read(~/.aws/**)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(git rebase *)",
      "Bash(wget *)",
      "Bash(npm publish:*)",
      "Bash(git commit *)",
      "Bash(gh pr merge *)"
    ]
  }
}

Skills (3)

Subagents (3)

doc-writer
model: inherit
Create or update exactly the requirements, architecture, and verbose implementation-plan documents for a feature. Use only after requirements are sufficiently refined.
requirements-refiner
model: inherit
Analyze pasted Jira SPD content or change requests, inspect repository context, identify gaps and contradictions, and interview the user until requirements are implementation-ready.
ticket-planner
model: inherit
Convert refined requirements into reviewable Jira ticket drafts using the repository ticket template. Use after requirements refinement or when the user supplies implementation-ready requirements.

Similar rigs

copied ✓