AGENT SKILLS · ミッション装備 / nikhilw

nikhilw · Agent Skills

出典を確認した実質的な文書を持つ Skill が 9 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。

nikhilw
コミュニティ

agentic-workflow

The Structured Agentic Development Workflow. Orchestrates brainstorm, write-plan, build-phase, 3p-review, triage, test-driven-development, systematic-debugging, and verify-completion skills. Use when starting new work, switching between development phases, or when the user asks about the workflow. A dedicated build model uses the build-model workflow instead of this one.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

brainstorm

Explore a problem space before planning. Proposes architectural approaches with trade-offs, challenges the obvious solution, estimates impact, and produces a decision document. Code is the LAST thing we touch — this skill never writes code or plans.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

build-phase

Execute one phase from a plan file using the TDD → Test → Self-Review loop. Use when a plan has been approved and it's time to build. Accepts a plan file path and phase number. Builds phase by phase and produces a build completion report. Review (/3p-review) and, for a dedicated build model, handoff (/handoff-summary) are driven by the orchestrating workflow (agentic-workflow for the main model, build-model for a dedicated build model), not by this skill.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

compact-brief

Write a one-line compact command for the user to run, and a resume brief to paste right after it, carrying what the rest of the workflow needs past a context compaction: where the work stands, the owner's rulings, what only ever lived in the conversation, and how the owner wants this model to work. Suggested at the workflow's two compact slots (plan approved, before the build; before verify-completion), and usable any time the user asks for a compact prompt.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

decision-summary

Summarise what has been decided so far, in plain words, from two angles, what the user will get and how it works. Use when the user asks for a summary, a recap, or "what did we decide", during or after a brainstorm or a plan discussion. It is a capability, not a phase; it changes nothing and the discussion can carry on after it.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

existing-mechanisms

The eight questions that must be answered about what a codebase already does before anything new is proposed, planned, or built, and the self-duplication inventory that catches a change duplicating its own code. Shared reference loaded by brainstorm, write-plan, build-phase and 3p-review. It is a reference, not a step of its own.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

knowledge-graph

How this workflow uses a graphify index: refreshing it, querying it, and the three limits on what a graph answer is worth, including why in typed code the count comes from the type checker, not the graph. Shared reference loaded by brainstorm and write-plan, and only when graphify is actually installed. It is a reference, not a step of its own.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

test-scope

How wide a test run must be at each gate of the workflow, what a run may execute, and when a run already made can be cited instead of re-run. Shared definition loaded by build-phase, 3p-review, build-model, verify-completion and agentic-workflow. It is a reference, not a step of its own.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日
nikhilw
コミュニティ

verify-completion

The final gate before any claim of "done", "fixed", or "passing", and before the commit or PR that closes the work. Runs three checks that nothing earlier in the workflow guarantees, a fresh full-suite result, a line-by-line tick-off of the plan's requirements, and a plan-drift audit from the decision document through the plan to the code. Evidence before assertions, always.

1時間の導入数
1
GitHub Stars
7
更新日
11月6日